Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-52j9-v3jc-9xgc

MEDIUMFix: tryton/trytond@11424d5

GHSA-52j9-v3jc-9xgc is a medium-severity (CVSS 5.3) Information Exposure vulnerability in trytond. O3 Security confirms whether GHSA-52j9-v3jc-9xgc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Tryton allows users to read the hashed password

Also known asCVE-2016-1241PYSEC-2016-12PYSEC-2016-40
Published
May 17, 2022
Updated
Nov 22, 2024
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 22, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

5 pkgs affected
🐍trytond🐍trytond🐍trytond🐍trytond🐍trytond

Real-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

Tryton 3.x before 3.2.17, 3.4.x before 3.4.14, 3.6.x before 3.6.12, 3.8.x before 3.8.8, and 4.x before 4.0.4 allow remote authenticated users to discover user password hashes via unspecified vectors.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPItrytond3.0.0&&< 3.2.173.2.17
🐍PyPItrytond3.4.0&&< 3.4.143.4.14
🐍PyPItrytond3.8.0&&< 3.8.83.8.8
🐍PyPItrytond3.6.0&&< 3.6.123.6.12
🐍PyPItrytond4.0.0&&< 4.0.44.0.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trytond. 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.

  2. Fix

    Update trytond to 3.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-52j9-v3jc-9xgc is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-52j9-v3jc-9xgc 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-52j9-v3jc-9xgc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Tryton 3.x before 3.2.17, 3.4.x before 3.4.14, 3.6.x before 3.6.12, 3.8.x before 3.8.8, and 4.x before 4.0.4 allow remote authenticated users to discover user password hashes via unspecified vectors.
O3 Security · Impact-Aware SCA

Is GHSA-52j9-v3jc-9xgc in your dependencies?

O3 detects GHSA-52j9-v3jc-9xgc across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.