Snyk Listing:- Cross-site Scripting (XSS) in angular | Snyk

Bug Fixes 

• $http: Fixed Cross-Site Scripting vulnerability (XSS). The $http service allowed JSONP requests with untrusted URLs which could be exploited by an attacker.  
  Use $sce.trustAsResourceUrl to handle JSONP sensitive operations. Ensure that the URL satisfies SCE.RESOURCE_URL. For more details, see SNYK-JS-ANGULAR-471879. 
• svg: Fixed Cross-Site Scripting vulnerability (XSS) through SVG files if enableSvg is set. For more details, see npm:angular:20180202. 
• $http: Fixed Cross-Site Scripting vulnerability (XSS). The $http service allowed JSON_CALLBACK placeholders which could be exploited by an attacker.  
  Specify the JSONP callback using the jsonpCallbackParam config. For more details, see npm:angular:20150315. 

NVD Listing: https://nvd.nist.gov/vuln/detail/CVE-2024-33599

nscd: Stack-based buffer overflow in netgroup cache

If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted
by client requests then a subsequent client request for netgroup data
may result in a stack-based buffer overflow.  This flaw was introduced
in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

NVD Listing: https://nvd.nist.gov/vuln/detail/CVE-2024-37891 

urllib3 is a user-friendly HTTP client library for Python. When using urllib3's proxy support with `ProxyManager`, the `Proxy-Authorization` header is only sent to the configured proxy, as expected. However, when sending HTTP requests *without* using urllib3's proxy support, it's possible to accidentally configure the `Proxy-Authorization` header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the `Proxy-Authorization` HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects. Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the `Proxy-Authorization` header during cross-origin redirects to avoid the small chance that users are doing this on accident. Users should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the `Proxy-Authorization` header, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach. We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited: 1. Setting the `Proxy-Authorization` header without using urllib3's built-in proxy support. 2. Not disabling HTTP redirects. 3. Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin. Users are advised to update to either version 1.26.19 or version 2.2.2. Users unable to upgrade may use the `Proxy-Authorization` header with urllib3's `ProxyManager`, disable HTTP redirects using `redirects=False` when sending requests, or not user the `Proxy-Authorization` header as mitigations.

NVD Listing: https://nvd.nist.gov/vuln/detail/CVE-2024-6345  

A vulnerability in the package_index module of pypa/setuptools versions up to 69.1.1 allows for remote code execution via its download functions. These functions, which are used to download packages from URLs provided by users or retrieved from package index servers, are susceptible to code injection. If these functions are exposed to user-controlled inputs, such as package URLs, they can execute arbitrary commands on the system. The issue is fixed in version 70.0.

NVD Listing: https://nvd.nist.gov/vuln/detail/CVE-2023-5129

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Duplicate of CVE-2023-4863.