Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2021-41130 State: PUBLISHED Published: 2021-10-07T18:30:17 Last Updated: 2024-08-04T02:59:31.599Z Severity: MEDIUM (CVSS 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) Vendors: cloudendpoints Products: esp Problem Types: CWE-290 Description: Extensible Service Proxy, a.k.a. ESP is a proxy which enables API management capabilities for JSON/REST or gRPC API services. ESPv1 can be configured to authenticate a JWT token. Its verified JWT claim is passed to the application by HTTP header "X-Endpoint-API-UserInfo", the application can use it to do authorization. But if there are two "X-Endpoint-API-UserInfo" headers from the client, ESPv1 only replaces the first one, the 2nd one wil
t if there are two "X-Endpoint-API-UserInfo" headers from the client, ESPv1 only replaces the first one, the 2nd one will be passed to the application. An attacker can send two "X-Endpoint-API-UserInfo" headers, the second one with a fake JWT claim. Application may use the fake JWT claim to do the authorization. This impacts following ESPv1 usages: 1) Users have configured ESPv1 to do JWT authentication with Google ID Token as described in the referenced google endpoint document. 2) Users backend application is using the info in the "X-Endpoint-API-UserInfo" header to do the authorization. It has been fixed by v1.58.0. You need to patch it in the following ways: * If your docker image is usi
e authorization. It has been fixed by v1.58.0. You need to patch it in the following ways: * If your docker image is using tag ":1", needs to re-start the container to pick up the new version. The tag ":1" will automatically point to the latest version. * If your docker image tag pings to a specific minor version, e.g. ":1.57". You need to update it to ":1.58" and re-start the container. There are no workaround for this issue. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/cloudendpoints/esp/security/advisories/GHSA-43wx-8qmj-9r9q - https://github.com/cloudendpoints/esp/commit/e310c4f91d229a072507f80c73811489b4cdff27 - https://cloud.google.com/endpoints/d
s://github.com/cloudendpoints/esp/commit/e310c4f91d229a072507f80c73811489b4cdff27 - https://cloud.google.com/endpoints/docs/openapi/authenticating-users-google-id - https://github.com/cloudendpoints/esp/releases/tag/v1.58.0
CVE ID: CVE-2021-41131 State: PUBLISHED Published: 2021-10-19T17:50:11 Last Updated: 2024-11-18T22:45:18.899Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N) Vendors: theupdateframework Products: python-tuf Problem Types: CWE-22 Description: python-tuf is a Python reference implementation of The Update Framework (TUF). In 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`). The
ecause the rolename is used to form the filename, and may contain path traversal characters (ie `../../name.json`). The impact is mitigated by a few facts: It only affects implementations that allow arbitrary rolename selection for delegated targets metadata, 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, The written file content is heavily restricted since it needs to be a valid, signed targets file. The file extension is always .json. A fix is available in version 0.19 or newer. There are no workarounds that do not require code changes. Clients can restrict the allowed character set for r
r newer. There are no workarounds 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. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr - https://github.com/theupdateframework/python-tuf/issues/1527 - https://github.com/theupdateframework/python-tuf/commit/4ad7ae48fda594b640139c3b7eae21ed5155a102
CVE ID: CVE-2021-41132 State: PUBLISHED Published: 2021-10-14T15:45:12 Last Updated: 2024-08-04T02:59:31.416Z Severity: CRITICAL (CVSS 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) Vendors: ome Products: omero-web Problem Types: CWE-116 Description: OMERO.web provides a web based client and plugin infrastructure. In versions prior to 5.11.0, a variety of templates do not perform proper sanitization through HTML escaping. Due to the lack of sanitization and use of ``jQuery.html()``, there are a whole host of cross-site scripting possibilities with specially crafted input to a variety of fields. This issue is patched in version 5.11.0. There are no known workarounds aside from upgrading. A
to a variety of fields. This issue is patched in version 5.11.0. There are no known workarounds aside from upgrading. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/ome/omero-web/security/advisories/GHSA-g67g-hvc3-xmvf - https://github.com/ome/omero-web/commit/0168067accde5e635341b3c714b1d53ae92ba424 - https://www.openmicroscopy.org/security/advisories/2021-SV3/
CVE ID: CVE-2021-41133 State: PUBLISHED Published: 2021-10-08T00:00:00 Last Updated: 2024-08-04T02:59:31.388Z Severity: HIGH (CVSS 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) Vendors: flatpak Products: flatpak Problem Types: CWE-20 Description: Flatpak is a system for building, distributing, and running sandboxed desktop applications on Linux. In versions prior to 1.10.4 and 1.12.0, Flatpak apps with direct access to AF_UNIX sockets such as those used by Wayland, Pipewire or pipewire-pulse can trick portals and other host-OS services into treating the Flatpak app as though it was an ordinary, non-sandboxed host-OS process. They can do this by manipulating the VFS using recent mount-rel
hough it was an ordinary, non-sandboxed host-OS process. They can do this by manipulating the VFS using recent mount-related syscalls that are not blocked by Flatpak's denylist seccomp filter, in order to substitute a crafted `/.flatpak-info` or make that file disappear entirely. Flatpak apps that act as clients for AF_UNIX sockets such as those used by Wayland, Pipewire or pipewire-pulse can escalate the privileges that the corresponding services will believe the Flatpak app has. Note that protocols that operate entirely over the D-Bus session bus (user bus), system bus or accessibility bus are not affected by this. This is due to the use of a proxy process `xdg-dbus-proxy`, whose VFS canno
accessibility bus are not affected by this. This is due to the use of a proxy process `xdg-dbus-proxy`, whose VFS cannot be manipulated by the Flatpak app, when interacting with these buses. Patches exist for versions 1.10.4 and 1.12.0, and as of time of publication, a patch for version 1.8.2 is being planned. There are no workarounds aside from upgrading to a patched version. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://github.com/flatpak/flatpak/security/advisories/GHSA-67h7-w3jq-vh4q - https://github.com/flatpak/flatpak/commit/1330662f33a55e88bfe18e76de28b7922d91a999 - https://github.com/flatpak/flatpak/commit/26b12484eb8a6219b9e7aa287
ak/commit/1330662f33a55e88bfe18e76de28b7922d91a999 - https://github.com/flatpak/flatpak/commit/26b12484eb8a6219b9e7aa287b298a894b2f34ca - https://github.com/flatpak/flatpak/commit/462fca2c666e0cd2b60d6d2593a7216a83047aaf - https://github.com/flatpak/flatpak/commit/4c34815784e9ffda5733225c7d95824f96375e36 - https://github.com/flatpak/flatpak/commit/89ae9fe74c6d445bb1b3a40e568d77cf5de47e48 - https://github.com/flatpak/flatpak/commit/9766ee05b1425db397d2cf23afd24c7f6146a69f - https://github.com/flatpak/flatpak/commit/a10f52a7565c549612c92b8e736a6698a53db330 - https://github.com/flatpak/flatpak/commit/e26ac7586c392b5eb35ff4609fe232c52523b2cf - https://lists.fedoraproject.org/archives/list/packag
m/flatpak/flatpak/commit/e26ac7586c392b5eb35ff4609fe232c52523b2cf - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/R5656ONDP2MGKIJMKEC7N2NXCV27WGTC/ - https://www.debian.org/security/2021/dsa-4984 - http://www.openwall.com/lists/oss-security/2021/10/26/9 - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T5DKCYRC6MFSTFCUP4DELCOUUP3SFEFX/ - https://security.gentoo.org/glsa/202312-12
CVE ID: CVE-2021-41134 State: PUBLISHED Published: 2021-11-03T17:50:10 Last Updated: 2024-08-04T02:59:31.698Z Severity: HIGH (CVSS 8.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Vendors: jupyter Products: nbdime Problem Types: CWE-79 Description: nbdime provides tools for diffing and merging of Jupyter Notebooks. In affected versions a stored cross-site scripting (XSS) issue exists within the Jupyter-owned nbdime project. It appears that when reading the file name and path from disk, the extension does not sanitize the string it constructs before returning it to be displayed. The diffNotebookCheckpoint function within nbdime causes this issue. When attempting to display the name of the lo
ayed. The diffNotebookCheckpoint function within nbdime causes this issue. When attempting to display the name of the local notebook (diffNotebookCheckpoint), nbdime appears to simply append .ipynb to the name of the input file. The NbdimeWidget is then created, and the base string is passed through to the request API function. From there, the frontend simply renders the HTML tag and anything along with it. Users are advised to patch to the most recent version of the affected product. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/jupyter/nbdime/security/advisories/GHSA-p6rw-44q7-3fw4 - https://github.com/jupyter/nbdime/commit/e44a5cc7677f24b45ebafc756db4
r/nbdime/security/advisories/GHSA-p6rw-44q7-3fw4 - https://github.com/jupyter/nbdime/commit/e44a5cc7677f24b45ebafc756db49058c2f750ea
CVE ID: CVE-2021-41135 State: PUBLISHED Published: 2021-10-20T18:05:10 Last Updated: 2024-08-04T02:59:31.625Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Vendors: cosmos Products: cosmos-sdk Problem Types: CWE-754 Description: The Cosmos-SDK is a framework for building blockchain applications in Golang. Affected versions of the SDK were vulnerable to a consensus halt due to non-deterministic behaviour in a ValidateBasic method in the x/authz module. The MsgGrant of the x/authz module contains a Grant field which includes a user-defined expiration time for when the authorization grant expires. In Grant.ValidateBasic(), that time is compared to the node’s local clo
n time for when the authorization grant expires. In Grant.ValidateBasic(), that time is compared to the node’s local clock time. Any chain running an affected version of the SDK with the authz module enabled could be halted by anyone with the ability to send transactions on that chain. Recovery would require applying the patch and rolling back the latest block. Users are advised to update to version 0.44.2. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-2p6r-37p9-89p2 - https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee - https://forum.cosmos.network/t/cosmos-sdk-vulnerability-re
/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee - https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349
CVE ID: CVE-2021-41136 State: PUBLISHED Published: 2021-10-12T15:30:11 Last Updated: 2025-05-27T15:16:10.431Z Severity: LOW (CVSS 3.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N) Vendors: puma Products: puma Problem Types: CWE-444 Description: Puma is a HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If the proxy use
The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If 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. This vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`. A
This vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/puma/puma/security/advisories/GHSA-48w2-rm65-62xx - https://github.com/puma/puma/commit/436c71807f00e07070902a03f79fd3e130eb6b18 - https://github.com/puma/puma/commit/acdc3ae571dfae0e045cf09a295280127db65c7f - https://github.com/puma/puma/commit/fb6ad8f8013ab5cdbb2f444cbfabd0b4fde71139
CVE ID: CVE-2021-41137 State: PUBLISHED Published: 2021-10-13T14:00:13 Last Updated: 2024-08-04T02:59:31.695Z Severity: HIGH (CVSS 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) Vendors: minio Products: minio Problem Types: CWE-285 Description: Minio is a Kubernetes native application for cloud storage. All users on release `RELEASE.2021-10-10T16-53-30Z` are affected by a vulnerability that involves bypassing policy restrictions on regular users. Normally, checkKeyValid() should return owner true for rootCreds. In the affected version, policy restriction did not work properly for users who did not have service (svc) or security token service (STS) accounts. This issue is fixed in `RELEASE
perly for users who did not have service (svc) or security token service (STS) accounts. This issue is fixed in `RELEASE.2021-10-13T00-23-17Z`. A downgrade back to release `RELEASE.2021-10-08T23-58-24Z` is available as a workaround. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/minio/minio/security/advisories/GHSA-v64v-g97p-577c - https://github.com/minio/minio/pull/13388 - https://github.com/minio/minio/pull/13422 - https://github.com/minio/minio/commit/415bbc74aacd53a120e54a663e941b1809982dbd
CVE ID: CVE-2021-41138 State: PUBLISHED Published: 2021-10-13T15:15:11 Last Updated: 2024-08-04T02:59:31.757Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) Vendors: paritytech Products: frontier Problem Types: CWE-20 Description: Frontier is Substrate's Ethereum compatibility layer. In 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. The attack is limited in that the signature is always validated, and the majority of the validat
nsactions into a block. The 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. The issue is patched in commit `146bb48849e5393004be5c88beefe76fdf009aba`. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/paritytech/frontier/security/advisories/GHSA-vj62-g63v-f8mf - https://github.com/paritytech/frontier/pull/497 - https://github.com/paritytech/frontier/commit/146bb48849e
-g63v-f8mf - https://github.com/paritytech/frontier/pull/497 - https://github.com/paritytech/frontier/commit/146bb48849e5393004be5c88beefe76fdf009aba
CVE ID: CVE-2021-41139 State: PUBLISHED Published: 2021-10-13T17:10:10 Last Updated: 2024-08-04T02:59:31.435Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) Vendors: anuko Products: timetracker Problem Types: CWE-79 Description: Anuko Time Tracker is an open source, web-based time tracking application written in PHP. When a logged on user selects a date in Time Tracker, it is being passed on via the date parameter in URI. Because of not checking this parameter for sanity in versions prior to 1.19.30.5600, it was possible to craft the URI with malicious JavaScript, use social engineering to convince logged on user to click on such link, and have the attacker-supplied J
us JavaScript, use social engineering to convince logged on user to click on such link, and have the attacker-supplied JavaScript to be executed in user's browser. This issue is patched in version 1.19.30.5600. As a workaround, one may introduce `ttValidDbDateFormatDate` function as in the latest version and add a call to it within the access checks block in time.php. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/anuko/timetracker/security/advisories/GHSA-h2v8-87c9-86cw - https://github.com/anuko/timetracker/commit/559906731f153c9b3a632c2839ed11669b76d593 - https://github.com/anuko/timetracker/commit/d3f60bd3e3ea8ff8ec31a596baec6750af601b7c
CVE ID: CVE-2021-41140 State: PUBLISHED Published: 2021-10-19T18:05:11 Last Updated: 2024-08-04T02:59:31.697Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Vendors: discourse Products: discourse-reactions Problem Types: CWE-668 Description: Discourse-reactions is a plugin for the Discourse platform that allows user to add their reactions to the post. In affected versions reactions given by user to secure topics and private messages are visible. This issue is patched in version 0.2 of discourse-reaction. Users who are unable to update are advised to disable the Discourse-reactions plugin in admin panel. Additional Analyst Notes: - CVE Program Container: References:
o disable the Discourse-reactions plugin in admin panel. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/discourse/discourse-reactions/security/advisories/GHSA-9358-hwg5-jrmh - https://github.com/discourse/discourse-reactions/commit/213d90b82fd15c4186ebc290fee18817d9727d0d
CVE ID: CVE-2021-41141 State: PUBLISHED Published: 2022-01-04T00:00:00.000Z Last Updated: 2025-04-23T19:15:38.851Z Severity: MEDIUM (CVSS 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: pjsip Products: pjproject Problem Types: CWE-667 Description: PJSIP is a free and open source multimedia communication library written in the C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In various parts of PJSIP, when error/failure occurs, it is found that the function returns without releasing the currently held locks. This could result in a system deadlock, which cause a denial of service for the users. No release has yet been made which contains t
esult in a system deadlock, which cause a denial of service for the users. No release has yet been made which contains the linked fix commit. All versions up to an including 2.11.1 are affected. Users may need to manually apply the patch. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/pjsip/pjproject/security/advisories/GHSA-8fmx-hqw7-6gmc - https://github.com/pjsip/pjproject/commit/1aa2c0e0fb60a1b0bf793e0d834073ffe50fb196 - https://lists.debian.org/debian-lts-announce/2022/03/msg00035.html - https://security.gentoo.org/glsa/202210-37
CVE ID: CVE-2021-41142 State: PUBLISHED Published: 2021-10-14T16:05:13 Last Updated: 2024-08-04T02:59:31.700Z Severity: MEDIUM (CVSS 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) Vendors: Enalean Products: tuleap Problem Types: CWE-79 Description: Tuleap Open ALM is a libre and open source tool for end to end traceability of application and system developments. There is a cross-site scripting vulnerability in Tuleap Community Edition prior to 12.11.99.25 and Tuleap Enterprise Edition 12.11-2. A malicious user with the capability to add and remove attachment to an artifact could force a victim to execute uncontrolled code. Tuleap Community Edition 11.17.99.146 and Tuleap Enterprise Editio
ct could force a victim to execute uncontrolled code. Tuleap Community Edition 11.17.99.146 and Tuleap Enterprise Edition 12.11-2 contain a fix for the issue. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/Enalean/tuleap/security/advisories/GHSA-p3j6-6h9h-34r5 - https://github.com/Enalean/tuleap/commit/d6c837ed6fa66d319175954a42f93d4d86745208 - https://tuleap.net/plugins/git/tuleap/tuleap/stable?a=commit&h=d6c837ed6fa66d319175954a42f93d4d86745208 - https://tuleap.net/plugins/tracker/?aid=22570
CVE ID: CVE-2021-41143 State: PUBLISHED Published: 2023-01-27T18:02:08.763Z Last Updated: 2025-03-10T21:18:37.767Z Severity: HIGH (CVSS 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) Vendors: OpenMage Products: magento-lts Problem Types: CWE-77 Description: OpenMage LTS is an e-commerce platform. Prior to versions 19.4.22 and 20.0.19, Magento admin users with access to the customer media could execute code on the server. Versions 19.4.22 and 20.0.19 contain a patch for this issue. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/OpenMage/magento-lts/security/advisories/GHSA-5vpv-xmcj-9q85 - https://github.com/OpenMage/magento-lts
ttps://github.com/OpenMage/magento-lts/security/advisories/GHSA-5vpv-xmcj-9q85 - https://github.com/OpenMage/magento-lts/commit/45330ff50439984e806992fa22c3f96c4d660f91 - https://github.com/OpenMage/magento-lts/releases/tag/v19.4.22 - https://github.com/OpenMage/magento-lts/releases/tag/v20.0.19
CVE ID: CVE-2021-41144 State: PUBLISHED Published: 2023-01-27T18:08:42.087Z Last Updated: 2025-03-10T21:18:31.922Z Severity: HIGH (CVSS 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) Vendors: OpenMage Products: magento-lts Problem Types: CWE-77 Description: OpenMage LTS is an e-commerce platform. Prior to versions 19.4.22 and 20.0.19, a layout block was able to bypass the block blacklist to execute remote code. Versions 19.4.22 and 20.0.19 contain a patch for this issue. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/OpenMage/magento-lts/security/advisories/GHSA-5j2g-3ph4-rgvm - https://github.com/OpenMage/magento-lts/commit/06
hub.com/OpenMage/magento-lts/security/advisories/GHSA-5j2g-3ph4-rgvm - https://github.com/OpenMage/magento-lts/commit/06c45940ba3256cdfc9feea12a3c0ca56d23acf8 - https://github.com/OpenMage/magento-lts/releases/tag/v19.4.22 - https://github.com/OpenMage/magento-lts/releases/tag/v20.0.19
CVE ID: CVE-2021-41145 State: PUBLISHED Published: 2021-10-25T22:05:11 Last Updated: 2024-08-04T02:59:31.586Z Severity: HIGH (CVSS 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H) Vendors: signalwire Products: freeswitch Problem Types: CWE-400 Description: FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. FreeSWITCH prior to version 1.10.7 is susceptible to Denial of Service via SIP flooding. When flooding FreeSWITCH with SIP messages, it was observed that after a number of seconds the process was killed by the operating system due to memory exhaustion. By abu