CVE-2022-2996 — python-scciclient
HIGHCVE-2022-2996 is a high-severity (CVSS 7.4) CWE-295 vulnerability in python-scciclient. A fix is available for python-scciclient — see the affected versions and patch details below.
python-scciclient vulnerable to Man-in-the-middle (MITM) attacks
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-2996 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
python-scciclientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
A flaw was found in the python-scciclient when making an HTTPS connection to a server where the server's certificate would not be verified. This issue opens up the connection to possible Man-in-the-middle (MITM) attacks.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | python-scciclient | all versions | 0.12.0pip install --upgrade 'python-scciclient==0.12.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for python-scciclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update python-scciclient to 0.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2996 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-2996 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-2996. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Ironic content for Red Hat OpenShift Container Platform 4.12 | crudini-0:0.9.3-4.el9 | RHSA-2022:7398 |
| Red Hat OpenStack Platform 16.1 | python-scciclient-0:0.9.1-2.20220111031440.el8ost | RHSA-2022:8868 |
| Red Hat OpenStack Platform 16.2 | python-scciclient-0:0.9.1-2.20220111031440.el8ost | RHSA-2022:8854 |
| Red Hat OpenStack Platform 17.0 | python-scciclient-0:0.10.2-0.20220830130628.b8e6e34.el9ost | RHSA-2023:0276 |
Frequently Asked Questions
Is CVE-2022-2996 in your dependencies?
O3 Security finds CVE-2022-2996 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.