CVE-2013-4374 json
An insecurity temporary file vulnerability exists in RHQ Mongo DB Drift Server through 2013-09-25 when unpacking zipped files.
published 7y ago modified 4mo ago also EUVD-2013-4256
- cvss
- 7.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
An insecurity temporary file vulnerability exists in RHQ Mongo DB Drift Server through 2013-09-25 when unpacking zipped files.
Is CVE-2013-4374 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-4374 updated cvss 3.2
Server: Malicious change set import due to insecure temporary file usage
-
Red Hat JBoss Operations Network 3 drift-mongodb drift-mongodbnot 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.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| NVD | 2.0 | 3.6 | AV:L/AC:L/Au:N/C:N/I:P/A:P |
Affected products
- RHQ Mongo DB Drift Server RHQ Mongo DB Drift Server
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2013-4374
issue-tracking, vendor-advisory
-
access.redhat.com
/security/cve/cve-2013-4374
vendor-advisory
Sources
- CVE List CVE-2013-4374
- NVD CVE-2013-4374
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.