dbcve.org
Rhq Mongo Db Drift ServerApplication · Redhat

CVE-2013-4374

HIGH · 7.1 CVSS v3.1 Published 2019-11-04
Fix available
A fix is available. Upgrade to after 2013-09-25 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An insecurity temporary file vulnerability exists in RHQ Mongo DB Drift Server through 2013-09-25 when unpacking zipped files.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A temporary file vulnerability exists in RHQ Mongo DB Drift Server where insecure handling of temporary files occurs during the unpacking of zipped files. This creates a race condition or predictable file location issue that could allow an attacker to inject malicious content or overwrite system files.

MitigationImplement secure temporary file handling using unique filenames, secure temporary directories with proper permissions, and atomic file operations. Update to a patched version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rhq Mongo Db Drift ServerApplication
Affected:<= 2013-09-25
Jboss Operations NetworkApplication
Affected:= 3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if RHQ Mongo DB Drift Server or JBoss Operations Network is installed
    Search for installation directories or check for packages named 'rhq-mongodb-drift-server' or 'jboss-operations-network' using your system's package manager or by searching for characteristic files such as drift-server JARs or the JBoss ON installation path.
    Affected if Either product is found on the system
  2. Determine the installed version of RHQ Mongo DB Drift Server
    Check the version metadata of the drift server component. Look in the installation directory for version files, MANIFEST.MF inside the drift server JAR, or check the RPM/package version if installed via yum/rpm.
    Affected if The version is dated 2013-09-25 or earlier, or the version cannot be determined but the product is present
  3. Determine the installed version of JBoss Operations Network
    Check the version of the JBoss Operations Network installation. Look for a version file in the JBoss ON installation root, or check the package version using 'rpm -qi jboss-operations-network' or similar command.
    Affected if The version is exactly 3.1
  4. Check if the Drift Server feature is enabled
    Examine the RHQ or JBoss ON configuration files for drift server settings. Look in conf/ or config/ directories for files containing 'drift' or 'mongodb' related configuration, and verify whether drift server components are configured to run.
    Affected if Drift server functionality is enabled in the configuration and either vulnerable version is installed
  5. Verify temporary file handling configuration
    Inspect the drift server or platform configuration for temporary file usage settings. Look for configurations specifying temp directories used during file extraction or unpacking operations.
    Affected if Temporary file handling is configured and the vulnerable versions are in use

The environment is affected if RHQ Mongo DB Drift Server with version dated 2013-09-25 or earlier, or JBoss Operations Network version 3.1, is installed with drift server functionality enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2013-09-25
Interim mitigation

Implement secure temporary file handling using unique filenames, secure temporary directories with proper permissions, and atomic file operations. Update to a patched version if available.

Fix this in Rhq Mongo Db Drift Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-4374 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data