CVE-2022-31733

{"id": "CVE-2022-31733", "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 3.9}]}, "published": "2023-02-03T19:15:11.107", "references": [{"url": "https://www.cloudfoundry.org/blog/cve-2022-31733-unsecured-application-port", "tags": ["Vendor Advisory"], "source": "security@vmware.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-295"}]}], "descriptions": [{"lang": "en", "value": "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."}], "lastModified": "2023-02-10T17:37:57.953", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:cloudfoundry:cf-deployment:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "5718F841-91E2-42C6-9567-96E87F3B152F", "versionEndIncluding": "23.2.0", "versionStartIncluding": "17.1"}, {"criteria": "cpe:2.3:a:cloudfoundry:diego:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "66BEABAD-95CF-44B2-AC3A-C950B0838E5D", "versionEndIncluding": "2.69.0", "versionStartIncluding": "2.55.0"}], "operator": "OR"}]}], "sourceIdentifier": "security@vmware.com"}