CVSS: 9.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-31733
https://notcve.org/view.php?id=CVE-2022-31733
Starting with diego-release 2.55.0 and up to 2.69.0, and starting with CF Deployment 17.1 and up to 23.2.0, apps are accessible via another port on diego cells, allowing application ingress without a client certificate. If mTLS route integrity is enabled AND unproxied ports are turned off, then an attacker could connect to an application that should be only reachable via mTLS, without presenting a client certificate. • https://www.cloudfoundry.org/blog/cve-2022-31733-unsecured-application-port • CWE-295: Improper Certificate Validation •
CVSS: 7.2EPSS: 0%CPEs: 2EXPL: 0CVE-2018-1265
https://notcve.org/view.php?id=CVE-2018-1265
Cloud Foundry Diego, release versions prior to 2.8.0, does not properly sanitize file paths in tar and zip files headers. A remote attacker with CF admin privileges can upload a malicious buildpack that will allow a complete takeover of a Diego Cell VM and access to all apps running on that Diego Cell. Cloud Foundry Diego, en versiones anteriores a la 2.8.0, no sanea correctamente las rutas de archivo en las cabeceras de archivos tar y zip. Un atacante remoto con privilegios de administrador CF puede subir un buildpack malicioso que permitirá la toma de control total de una máquina virtual Diego Cell, así como el acceso a todas las aplicaciones que se ejecuten en esa Diego Cell. • https://www.cloudfoundry.org/blog/cve-2018-1265 • CWE-434: Unrestricted Upload of File with Dangerous Type •