Ansible Automation PlatformApplication · Redhat
CVE-2023-50782
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 · uneditedA flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.
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 · moderate confidenceThe python-cryptography package contains a vulnerability that allows a remote attacker to decrypt captured TLS messages when RSA key exchange is used. This appears to be a variant of an oracle attack (likely related to Lucky Thirteen or Bleichenbacher-style attacks) against RSA-based TLS handshakes, enabling recovery of sensitive data from previously captured encrypted traffic.
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
Ansible Automation PlatformApplication
= 2.0
Enterprise LinuxOperating system
= 8.0= 9.0
Update InfrastructureApplication
= 4
CryptographyApplication
< 42.0.0= 7.6.0= 7.6.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 python-cryptography versionRun 'pip show cryptography' or check your package manager for the installed version of the python-cryptography packageAffected if The installed version is less than 42.0.0 (for cryptography.io package) or matches the specific Redhat/Couchbase product versions listed (2.0, 8.0, 9.0, 4, 7.6.0, 7.6.1)
-
Determine if TLS with RSA key exchange is in useReview your TLS/SSL server configuration and identify which key exchange methods are enabled. Check cipher suite settings for RSA-based key exchange ciphers (such as TLS_RSA_WITH_*)Affected if RSA key exchange ciphers are enabled and the server accepts RSA key exchange in TLS handshakes
-
Check product-specific package versionsFor Redhat products (Ansible Automation Platform 2.0, RHEL 8.0/9.0, RHUI 4) and Couchbase Server (7.6.0, 7.6.1), verify the version of the python-cryptography package bundled or installedAffected if The product version matches the affected versions and uses an older python-cryptography package
-
Inspect TLS handshake configurationCapture or review TLS handshake logs or configuration to confirm RSA key exchange is being offered/accepted by the serverAffected if TLS connections use RSA key exchange rather than ephemeral Diffie-Hellman (DHE/ECDHE) which provides forward secrecy
You are affected if python-cryptography version is below 42.0.0 (or matches the specific Redhat/Couchbase versions) AND your TLS configuration enables RSA key exchange ciphers.
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 data42.0.0
Upgrade python-cryptography to the latest patched version. If immediate patching is not possible, consider temporarily disabling RSA key exchange in favor of ephemeral Diffie-Hellman (DHE/ECDHE) cipher suites, and ensure TLS sessions use forward secrecy.
Fix this in Ansible Automation Platform
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50782 — 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-2023-50782 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