GHSA-4fjv-pmhg-3rfg is a medium-severity (CVSS 6.8) CWE-325 vulnerability in oic. O3 Security confirms whether GHSA-4fjv-pmhg-3rfg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Multiple cryptographic issues in Python oic
Real-World Exposure
oicReal-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
Impact
- Client implementations using this library
Issues
- The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg.
- JWA
nonealgorithm was allowed in all flows. oic.consumer.Consumer.parse_authzreturns an unverified IdToken. The verification of the token was left to the discretion of the implementator.iatclaim was not checked for sanity (i.e. it could be in the future)
Patches
- IdToken signature is now always checked.
- JWA
nonealgorithm is now allowed only if using theresponse_typecode - IdToken verification is now done automatically.
iatclaim is now checked for sanity.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | oic | all versions | 1.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oic. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update oic to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4fjv-pmhg-3rfg 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 pinpoints whether GHSA-4fjv-pmhg-3rfg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-4fjv-pmhg-3rfg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4fjv-pmhg-3rfg in your dependencies?
O3 detects GHSA-4fjv-pmhg-3rfg across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.