CVE-2014-125056 json
Pylons horus services.py timing discrepancy
published 3y ago modified 4mo ago also EUVD-2014-1226
- cvss
- 2.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
A vulnerability was found in Pylons horus and classified as problematic. Affected by this issue is some unknown functionality of the file horus/flows/local/services.py. The manipulation leads to observable timing discrepancy. The complexity of an attack is rather high. The exploitation is known to be difficult. The patch is identified as fd56ccb62ce3cbdab0484fe4f9c25c4eda6c57ec. It is recommended to apply a patch to fix this issue. VDB-217598 is the identifier assigned to this vulnerability.
Patch / fix
Is CVE-2014-125056 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.6 | CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.0 | 2.6 | CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 2.0 | 1.4 | AV:A/AC:H/Au:S/C:P/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Pylons horus
Classification
- Weakness
-
- CWE-208 Observable Timing Discrepancy
References
-
github.com
/Pylons/horus/commit/fd56ccb62ce3cbdab0484fe4f9c25c4eda6c57ec
patch, third-party-advisory
-
vuldb.com
/?id.217598
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.217598
signature, permissions-required, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2014-125056
- NVD CVE-2014-125056
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.