CVE-2013-0264 json
An import error was introduced in Cumin in the code refactoring in r5310.
published 6y ago modified 4mo ago also EUVD-2013-0292
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
An import error was introduced in Cumin in the code refactoring in r5310. Server certificate validation is always disabled when connecting to Aviary servers, even if the installed packages on a system support it.
Patch / fix
Is CVE-2013-0264 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-0264 updated cvss 4.8
cumin: server certificate validation is always disabled when connecting to Aviary servers
-
Red Hat Enterprise MRG 1 cumin Red Hat Enterprise MRG 2 cuminnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- cumin cumin
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2013-0264
issue-tracking, patch, vendor-advisory
-
access.redhat.com
/security/cve/cve-2013-0264
vendor-advisory
Sources
- CVE List CVE-2013-0264
- NVD CVE-2013-0264
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.