CVE-2013-1793 json
openstack-utils openstack-db has insecure password creation
published 6y ago modified 4mo ago also EUVD-2013-1817
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
openstack-utils openstack-db has insecure password creation
Is CVE-2013-1793 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-1793 updated cvss 5.0
openstack-utils: openstack-db insecure password creation for services
-
Red Hat OpenStack Platform 3 openstack-utilsaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) openstack-utils Red Hat OpenStack Platform 4 openstack-utilsnot 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
1.03% chance of exploitation in the next 30 days, higher than 63% 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:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- openstack-utils openstack-db program
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2013-1793
issue-tracking, vendor-advisory
-
access.redhat.com
/security/cve/cve-2013-1793
vendor-advisory
Sources
- CVE List CVE-2013-1793
- NVD CVE-2013-1793
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.