Advisory Database Sync

This commit is contained in:
advisory-database[bot]
2024-12-04 05:20:51 +00:00
parent a1ef4a1f84
commit 6845970f28
940 changed files with 1253 additions and 3759 deletions
@@ -3,14 +3,10 @@
"id": "GHSA-2w8g-m5j8-7m87",
"modified": "2022-01-10T21:37:04Z",
"published": "2022-01-12T21:45:59Z",
"aliases": [
],
"aliases": [],
"summary": "Zalgo-like output that crashes the server",
"details": "### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\n[`colors`](https://npmjs.com/package/colors) package caused zalgo-like output (see https://github.com/soketi/soketi/issues/276, https://github.com/Marak/colors.js/issues/289), breaking the servers.\n\n**Only NPM users that recently upgraded or installed the NPM package are affected.**\n\nDocker users seem to not be affected as the dependencies were bundled at the time of the build, which were tested.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nLatest patch. `0.26.1` to be exact at the time of writing.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nYou cannot get around this as it's related to dependencies.\n\n### References\n_Are there any links users can visit to find out more?_\n\n- https://github.com/Marak/colors.js/issues/289\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the issues board](https://github.com/soketi/soketi/issues)\n* Email us at [alex@renoki.org](mailto:alex@renoki.org)\n",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -39,9 +35,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "CRITICAL",
"github_reviewed": true,
"github_reviewed_at": "2022-01-10T21:37:04Z",
@@ -3,14 +3,10 @@
"id": "GHSA-5rqg-jm4f-cqx7",
"modified": "2022-01-10T19:56:36Z",
"published": "2022-01-10T17:29:53Z",
"aliases": [
],
"aliases": [],
"summary": "Infinite loop causing Denial of Service in colors",
"details": "colors is a library for including colored text in node.js consoles. Between 07 and 09 January 2022, colors versions 1.4.1, 1.4.2, and 1.4.44-liberty-2 were published including malicious code that caused a Denial of Service due to an infinite loop. Software dependent on these versions experienced the printing of randomized characters to console and an infinite loop resulting in unbound system resource consumption.\n\nUsers of colors relying on these specific versions should downgrade to version 1.4.0.\n",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -3,14 +3,10 @@
"id": "GHSA-5rrq-pxf6-6jx5",
"modified": "2022-01-07T22:20:53Z",
"published": "2022-01-08T00:22:42Z",
"aliases": [
],
"aliases": [],
"summary": "Prototype Pollution in node-forge debug API.",
"details": "### Impact\nThe `forge.debug` API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way.\n\n### Patches\nThe `forge.debug` API and related functions were removed in 1.0.0.\n\n### Workarounds\nDon't use the `forge.debug` API directly or indirectly with untrusted input.\n\n### References\n- https://www.huntr.dev/bounties/1-npm-node-forge/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [forge](https://github.com/digitalbazaar/forge).\n* Email us at support@digitalbazaar.com.",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -69,9 +69,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2022-01-11T18:50:39Z",
@@ -8,9 +8,7 @@
],
"summary": "Cross-site Scripting in Scratch-Svg-Renderer",
"details": "A DOM-based cross-site scripting (XSS) vulnerability in Scratch-Svg-Renderer v0.2.0 allows attackers to execute arbitrary web scripts or HTML via a crafted sb3 file.",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -8,9 +8,7 @@
],
"summary": "Cross-site Scripting in Apache Pluto",
"details": "The input fields in the JSP version of the Apache Pluto Applicant MVCBean CDI portlet are vulnerable to Cross-Site Scripting (XSS) attacks. Users should migrate to version 3.1.1 of the applicant-mvcbean-cdi-jsp-portlet.war artifact",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -3,14 +3,10 @@
"id": "GHSA-m6w8-fq7v-ph4m",
"modified": "2022-01-12T21:38:27Z",
"published": "2022-01-13T16:09:36Z",
"aliases": [
],
"aliases": [],
"summary": "GovernorCompatibilityBravo incorrect ABI encoding may lead to unexpected behavior",
"details": "### Impact\n\nThe `GovernorCompatibilityBravo` module may lead to the creation of governance proposals that execute function calls with incorrect arguments due to bad ABI encoding. This happens if the proposal is created using explicit function signatures, e.g. a proposal to invoke the function `foo(uint256)` is created as `propose([target], [0], [\"foo(uint256)\"], [\"0x00..01\"])`. If the function selector is provided as part of the encoded proposal data the issue is not present, e.g. the same proposal is created as `propose([target], [0], [\"0x2fbebd3800..01\"])`, where `2fbebd38` is the function selector.\n\nWe've assessed the instances of this contract found on chain, and did not find any occurrence of this bug in the past. Proposal creation through Tally or OpenZeppelin Defender is not affected. The core `Governor` contract on its own is not affected.\n\n### Patches\n\nA fix is included in version v4.4.2 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.\n\n### Workarounds\n\nDo not create proposals using explicit function signatures. Instead, use the `propose` function without the `signatures` argument, and create the proposal using the fully ABI-encoded function call including the function selector in the `calldatas` argument as explained above.\n\n### References\n\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/issues/3099\n\n### Credits\n\nThis issue was identified and reported by @GeraldHost.\n\n### For more information\n\nIf you have any questions, comments, or need assistance regarding this advisory, email us at security@openzeppelin.com.\n\nTo submit security reports please use [our bug bounty on Immunefi](https://immunefi.com/bounty/openzeppelin/).",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -62,9 +58,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2022-01-11T23:50:55Z",
@@ -3,14 +3,10 @@
"id": "GHSA-m7vp-hqwv-7m5x",
"modified": "2022-01-11T16:45:39Z",
"published": "2022-01-12T22:33:04Z",
"aliases": [
],
"aliases": [],
"summary": "Unbounded memory usage on exposed HTTP/2 (non-gRPC) endpoints",
"details": "### Impact\nThe net/http Go package has a reported vulnerability tracked under CVE-2021-44716 which allows attacker controlled HTTP/2 requests to trigger unbounded memory usage in HTTP/2 endpoints. gRPC endpoints are not vulnerable as they rely on their own HTTP/2 implementation instead of the net/http package. HTTP/2 endpoints consuming the net/http package within SPIRE server and agent (or other components in this repository) that are _on by default_ include the following:\n- OIDC Discovery Provider\n- K8s Workload Registrar in webhook mode\n\nThe following endpoints are vulnerable _when enabled_:\n- SPIRE server bundle endpoint (i.e. Federation API)\n\nThe following endpoints are _NOT_ vulnerable, since HTTP/2 support in go is not enabled on non-TLS protected endpoints:\n- SPIRE server/agent metrics endpoint when configured for Prometheus\n- SPIRE server/agent health endpoints\n- SPIRE server/agent profiling endpoints\n\n### Patches\nSPIRE 1.0.3 and 1.1.3 have been released with an upgraded Go toolchain which patches the vulnerability\n\n### Workarounds\nThe vulnerability can be worked around entirely by including the `http2server=0` value in the `GODEBUG` environment variable (see https://github.com/golang/go/issues/50058). This turns off HTTP/2 support on all non-gRPC endpoints. They will still function with HTTP/1.1.\n\nThe risk associated with this vulnerability can be somewhat mitigated by limiting the exposure of the endpoints in question. If necessary, vulnerable components or endpoints that are optionally configured can be disabled temporarily.\n\n### References\n- https://github.com/golang/go/issues/50058\n- https://go-review.googlesource.com/c/go/+/370574/\n- https://nvd.nist.gov/vuln/detail/CVE-2021-44716\n",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -58,9 +54,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2022-01-10T22:07:35Z",
@@ -3,9 +3,7 @@
"id": "GHSA-rrgw-3hg3-9x8c",
"modified": "2022-01-10T21:39:18Z",
"published": "2022-01-12T21:49:49Z",
"aliases": [
],
"aliases": [],
"summary": "XSS vulnerability in translations",
"details": "### Summary\n\nAn attacker with admin privileges and access to Translations management functionality may add JS payload to translation values via: \n - Translation management UI.\n - Translations downloaded via the Crowdin service may also contain JS strings used for XSS attacks, for a successful attack poisoned translation should be enabled, downloaded, and installed.\n - Translations uploaded via Upload translation file on the All Languages grid\n\n### Workarounds\n\nThere are no workarounds that address this vulnerability.",
"severity": [
@@ -80,9 +78,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2022-01-10T21:39:18Z",
@@ -3,14 +3,10 @@
"id": "GHSA-wxgw-qj99-44c2",
"modified": "2022-01-07T22:20:50Z",
"published": "2022-01-08T00:22:40Z",
"aliases": [
],
"aliases": [],
"summary": "Prototype Pollution in node-forge util.setPath API",
"details": "### Impact\n`forge.util.setPath` had a potential prototype pollution issue if called with untrusted keys. This API was not used by forge itself.\n\n### Patches\nThe `forge.util.setPath` API and related functions were removed in 0.10.0.\n\n### Workarounds\nDon't call `forge.util.setPath` directly or indirectly with untrusted keys.\n\n### References\n- https://security.snyk.io/vuln/SNYK-JS-NODEFORGE-598677\n- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7720\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [forge](https://github.com/digitalbazaar/forge).\n* Email us at support@digitalbazaar.com.",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -39,9 +35,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "LOW",
"github_reviewed": true,
"github_reviewed_at": "2022-01-07T22:20:50Z",
@@ -8,9 +8,7 @@
],
"summary": "Cross-site Scripting in Apache Pluto",
"details": "The input fields of the Apache Pluto UrlTestPortlet are vulnerable to Cross-Site Scripting (XSS) attacks. Users should migrate to version 3.1.1 of the v3-demo-portlet.war artifact",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -3,9 +3,7 @@
"id": "GHSA-xh99-hw7h-wf63",
"modified": "2022-01-13T22:08:36Z",
"published": "2022-01-13T22:25:44Z",
"aliases": [
],
"aliases": [],
"summary": "Unchecked validity of Facing values in PlayerActionPacket",
"details": "### Impact\nA remote attacker may crash a server by sending `PlayerActionPacket` with invalid facing values (e.g. negative), specifically with `START_BREAK` or `CRACK_BLOCK` actions, or with a `UseItemTransactionData` (typically in `InventoryTransactionPacket`).\n\n### Patches\nf126479c37ff00a717a828f5271cf8e821d12d6c\n\n### Workarounds\nUsing a plugin, cancel `DataPacketReceiveEvent` if the packet is `PlayerActionPacket` and the facing is outside the range 0-5 when receiving START_BREAK or CRACK_BLOCK actions, or UseItemTransactionData. However, beware that negative values may be legitimate in some cases.\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)\n",
"severity": [
@@ -50,9 +48,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2022-01-13T22:08:36Z",
@@ -4,9 +4,7 @@
"modified": "2024-05-20T21:04:24Z",
"published": "2022-02-12T00:00:36Z",
"withdrawn": "2024-05-20T21:04:24Z",
"aliases": [
],
"aliases": [],
"summary": "Duplicate Advisory: TLS certificate validation error in mellium.im/xmpp",
"details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-h289-x5wc-xcv8. This link is maintained to preserve external references.\n\n## Original Description\nIn Mellium mellium.im/xmpp through 0.21.0, an attacker capable of spoofing DNS TXT records can redirect a WebSocket connection request to a server under their control without causing TLS certificate verification to fail. This occurs because the wrong host name is selected during this verification.",
"severity": [
@@ -3,9 +3,7 @@
"id": "GHSA-rpx7-33j2-xx9x",
"modified": "2022-01-07T22:34:36Z",
"published": "2022-02-15T01:57:18Z",
"aliases": [
],
"aliases": [],
"summary": "Arbitrary file deletion in NeMo ASR webapp",
"details": "### Description\n\nNVIDIA NeMo contains a vulnerability in ASR WebApp, where Relative Path Traversal (CWE-23) may lead to deletion of any directory through the \"../\" structure when admin privileges are available.\n\nCVSS Score = 2.0\nhttps://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N\n\n### Impact\nWhen the optional tool ASR Webapp (https://github.com/NVIDIA/NeMo/tree/main/tools/asr_webapp) is used prior to commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0, some interfaces do not verify user input. Malicious attackers can construct malicious requests to delete any directory through the \"../\" structure.\n\nThe vulnerability affects only cases where this particular web app is started by a user with superuser permissions. The web application is *not* a part of the regular pip release or the corresponding container, and impacts only users that clone the repository in its entirety and execute the web app (while also possessing superuser permissions).\n\n## Patches\n\nThis vulnerability has been patched via https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0, which is effectively any clone of the repository post r1.5.1 branch. Since the web app is not distributed via pip release or container, users who clone the main branch post this commit will possess the patch.\n\n### Workarounds\nThe changes in commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0 can be applied to any version of the web app without any adverse effect.\n\n### Additional Information\nExploit Found on: 2021.12.16\nExploit Found by: @haby0\n\n",
"severity": [
@@ -50,9 +48,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "LOW",
"github_reviewed": true,
"github_reviewed_at": "2022-01-07T22:34:36Z",
@@ -51,9 +51,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "CRITICAL",
"github_reviewed": true,
"github_reviewed_at": "2023-07-11T00:21:33Z",
@@ -3,9 +3,7 @@
"id": "GHSA-hj8m-9fhf-v7jp",
"modified": "2023-06-23T21:46:11Z",
"published": "2023-06-23T21:46:11Z",
"aliases": [
],
"aliases": [],
"summary": "fief-server Server-Side Template Injection vulnerability",
"details": "# Server-Side Template Injection\n\n## Overview of the Vulnerability\n\nServer-Side Template Injection (SSTI) is a vulnerability within application templating engines where user input is improperly handled and is embedded into the template, possibly leading code being executed.\n\nAn attacker can use SSTI to execute code on the underlying system by manipulating values within the embedded template. When code is executed within the underlying system, it can allow an attacker to run permissioned commands under the exploited process, or exploit Cross-Site Scripting (XSS) to run code within the user's browser.\n\n## Business Impact\n\nSSTI can lead to reputational damage for the business due to a loss in confidence and trust by users. If an attacker successfully executes code within the underlying system, it can result in data theft and indirect financial losses.\n\n## Steps to Reproduce\n\n1. [Sign up](https://fief.fief.dev/register) and login to your account\n1. Use a browser to navigate to: email-templates {{[URL](https://test.fief.dev/admin/customization/email-templates/)}}\n1. put your payload in Edit Base template `{{ cycler.__init__.__globals__.os.popen('id').read() }}` and you will se it will execute.\n\nPayload:\n`{{ cycler.__init__.__globals__.os.popen('id').read() }}`\n\n## Proof of Concept (PoC)\n\nThe screenshot(s) below demonstrates the SSTI:\n\n![SSTI](https://user-images.githubusercontent.com/42150485/248214990-854c2272-4f34-4c49-9759-d49ce8ce3d12.png)\n",
"severity": [
@@ -61,9 +59,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "CRITICAL",
"github_reviewed": true,
"github_reviewed_at": "2023-06-23T21:46:11Z",
@@ -3,9 +3,7 @@
"id": "GHSA-m8v7-469p-5x89",
"modified": "2023-07-25T14:44:27Z",
"published": "2023-07-25T14:44:27Z",
"aliases": [
],
"aliases": [],
"summary": "Hard-coded System User Credentials in Folio Data Export Spring module ",
"details": "### Impact\nThe module creates a system user that is used to perform internal module-to-module operations. Credentials for this user are hard-coded in the source code. This makes it trivial to authenticate as this user, allowing unauthorized read access to these mod-inventory-storage records: instances, holdings, items, contributor-types, identifier-types. This includes records marked as suppressed from discovery.\n\n### Patches\nUpgrade mod-remote-storage to >=2.0.3, or a 1.7.x version >=1.7.1.\n\n### Workarounds\nNo known workarounds.\n\n### References\nhttps://wiki.folio.org/x/hbMMBw - FOLIO Security Advisory with Upgrade Instructions\nhttps://github.com/folio-org/mod-remote-storage/commit/57df495f76e9aa5be9ce7ce3a65f89b6dbcbc13b - Fix",
"severity": [
@@ -73,9 +71,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2023-07-25T14:44:27Z",
@@ -3,9 +3,7 @@
"id": "GHSA-vf78-3q9f-92g3",
"modified": "2023-07-25T13:53:42Z",
"published": "2023-07-25T13:53:42Z",
"aliases": [
],
"aliases": [],
"summary": "Hard-coded System User Credentials in Folio Data Export Spring module ",
"details": "### Impact\nThe module creates a system user that is used to perform internal module-to-module operations. Credentials for this user are hard-coded in the source code. This makes it trivial to authenticate as this user, resulting in unauthorized access to potentially dangerous APIs, allowing to view and modify configuration including single-sign-on configuration, to read, add and modify user data, and to read and transfer fees/fines in a patron's account.\n\n### Patches\nUpgrade mod-data-export-spring to >=2.0.2, or a 1.5.x version >=1.5.4.\n\n### Workarounds\nNo known workarounds.\n\n### References\nhttps://wiki.folio.org/x/hbMMBw - FOLIO Security Advisory with Upgrade Instructions\nhttps://github.com/folio-org/mod-data-export-spring/commit/93aff4566bff59e30f4121b5a2bda5b0b508a446 - Fix",
"severity": [
@@ -73,9 +71,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "CRITICAL",
"github_reviewed": true,
"github_reviewed_at": "2023-07-25T13:53:42Z",
@@ -62,9 +62,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "CRITICAL",
"github_reviewed": true,
"github_reviewed_at": "2023-09-25T18:46:08Z",
@@ -3,14 +3,10 @@
"id": "GHSA-4qpj-gxxg-jqg4",
"modified": "2024-05-29T13:13:16Z",
"published": "2024-05-29T13:13:16Z",
"aliases": [
],
"aliases": [],
"summary": "Swiftmailer Sendmail transport arbitrary shell execution",
"details": "Prior to 5.2.1, the sendmail transport (`Swift_Transport_SendmailTransport`) was vulnerable to an arbitrary shell execution if the \"From\" header came from a non-trusted source and no \"Return-Path\" is configured. This has been fixed in 5.2.1. If you are using sendmail as a transport, you are encouraged to upgrade as soon as possible.",
"severity": [
],
"severity": [],
"affected": [
{
"package": {
@@ -59,9 +55,7 @@
}
],
"database_specific": {
"cwe_ids": [
],
"cwe_ids": [],
"severity": "CRITICAL",
"github_reviewed": true,
"github_reviewed_at": "2024-05-29T13:13:16Z",

Some files were not shown because too many files have changed in this diff Show More