CVE-2022-31733
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStarting 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn affected diego-release and CF Deployment versions, when mTLS route integrity is enabled and unproxied ports are disabled, applications are accessible through an alternate port on Diego cells without requiring a client certificate. This allows attackers to bypass mTLS authentication and connect to protected applications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 17.1, <= 23.2.0>= 2.55.0, <= 2.69.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify diego-release versionRun 'bosh -d deployment-name ssh diego-cell/0 "cat /var/vcap/packages/diego-release/.version"' or check your deployment manifest for the diego-release release versionAffected if Version is between 2.55.0 and 2.69.0 inclusive
-
Identify CF Deployment versionRun 'bosh deployments' or check the cf-deployment.yml version file in your deployment repositoryAffected if Version is between 17.1 and 23.2.0 inclusive
-
Check if mTLS route integrity is enabledInspect your diego-cell deployment manifest or runtime config for the property 'diego.route_emitter.mtls_enable' set to true, or check for 'mtls_mode: mutual' in your gorouter configurationAffected if mtls_enable is true or mtls_mode is set to mutual
-
Check if unproxied ports are disabledInspect the diego-cell manifest for 'diego.rep.unproxied_port' setting - if it is set to 0 or removed/unset, unproxied ports are disabled. Run 'bosh -d deployment-name ssh diego-cell/0 "netstat -tulpn | grep LISTEN"' to verify no direct app ports are exposedAffected if unproxied_port is set to 0 or is absent, and direct ports on Diego cells are not listening externally
-
Verify alternate port exposureFrom an external host without a client certificate, attempt to curl an application through the Diego cell IP directly on common alternate ports (such as 8080, 60000-60010 range). Check if the app responds without presenting a client certificateAffected if Applications respond on alternate ports without mTLS certificate authentication
You are affected if you run diego-release 2.55.0-2.69.0 or CF Deployment 17.1-23.2.0, with mTLS route integrity enabled and unproxied ports disabled, allowing unauthenticated access to apps via alternate ports.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade diego-release to version 2.70.0 or later, and upgrade CF Deployment to version 23.3.0 or later. Alternatively, review and adjust the configuration of mTLS route integrity and unproxied port settings until patching can be completed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31733 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data