dbcve.org
Mod Ruid2Application · Mod Ruid2 Project

CVE-2013-1889

HIGH · 7.5 CVSS v3.1 Published 2019-11-08
Fix available
A fix is available. Upgrade to 0.9.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
mod_ruid2 before 0.9.8 improperly handles file descriptors which allows remote attackers to bypass security using a CGI script to break out of the chroot.

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

mod_ruid2 before 0.9.8 contains a file descriptor handling flaw that allows CGI scripts to escape the chroot sandbox, enabling remote attackers to bypass security restrictions and potentially access unauthorized resources outside the intended jail.

MitigationUpgrade mod_ruid2 to version 0.9.8 or later to patch the file descriptor handling vulnerability. Alternatively, review the necessity of mod_ruid2 and consider using alternative isolation mechanisms if the module is not actively maintained.

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
Mod Ruid2Application
Affected:< 0.9.8

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Verify mod_ruid2 is installed
    Check your Apache configuration files (httpd.conf, apache2.conf, or included conf files) for a LoadModule directive loading mod_ruid2, such as 'LoadModule ruid2_module modules/mod_ruid2.so' or 'LoadModule ruid2_module modules/mod_ruid2.c'. Also check for any 'ruid2' references in loaded modules via 'apachectl -M' or 'httpd -M'.
    Affected if mod_ruid2 is not loaded - the vulnerability does not apply
  2. Determine installed mod_ruid2 version
    Check the mod_ruid2 module file itself for version information. Common locations include /usr/lib/apache2/modules/mod_ruid2.so or similar paths. Use 'strings' command on the .so file to find version strings, or check the source file if compiled from source (mod_ruid2.c typically contains version defines near the top). Compare the found version against 0.9.8.
    Affected if version is below 0.9.8 - the vulnerable version is present
  3. Confirm CGI script execution is enabled
    Check Apache configuration for CGI-related directives. Look for 'ScriptAlias' directives, 'AddHandler cgi-script', or '<FilesMatch \.cgi>' blocks. Also verify if the directory containing CGI scripts has 'Options +ExecCGI' and 'AllowOverride None' with 'Require all granted'.
    Affected if CGI scripts are enabled - the attack vector is present
  4. Check if chroot isolation is configured with mod_ruid2
    Examine mod_ruid2 configuration directives in Apache config files. Look for RuidChrootDir directive which defines the chroot jail path, or RuidDocRoot which may indicate document root mapping. Also check for any 'mod_ruid2' include files in /etc/apache2/mods-enabled/ or similar locations.
    Affected if chroot is configured via RuidChrootDir or RuidDocRoot - the escape vulnerability is relevant

Your environment is affected if mod_ruid2 is loaded with a version below 0.9.8, CGI execution is enabled, and chroot isolation is configured - all three conditions must be present for the chroot escape to be exploitable.

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 0.9.8 or later
Fixed in 0.9.8
Interim mitigation

Upgrade mod_ruid2 to version 0.9.8 or later to patch the file descriptor handling vulnerability. Alternatively, review the necessity of mod_ruid2 and consider using alternative isolation mechanisms if the module is not actively maintained.

Fix this in Mod Ruid2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1889 — 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-1889 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