dbcve.org
RmakeApplication · Rpath

CVE-2007-5194

MEDIUM · 6.9 CVSS v2.0 Published 2007-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
The Chroot server in rMake 1.0.11 creates a /dev/zero device file with read/write permissions for the rMake user and the same minor device number as /dev/port, which might allow local users to gain root privileges.

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 · high confidence

The rMake 1.0.11 chroot server creates a /dev/zero device file with read/write permissions for the rMake user and assigns it the same minor device number as /dev/port. This misconfiguration allows local users to potentially manipulate device files within the chroot environment to escalate privileges to root.

MitigationRestrict or remove the /dev/zero device file creation in the chroot environment, or implement proper device file permission controls and avoid using matching minor device numbers with system devices.

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
RmakeApplication
Affected:= 1.0.11

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/Au:N/C:C/I:C/A:C

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. Check installed rMake version
    Run 'rpm -q rmake' or check package management system for rmake version 1.0.11
    Affected if Version 1.0.11 is installed
  2. Locate rMake chroot environment
    Search for /rmake/chroot or similar rMake chroot directories, commonly under /var/lib/rmake or /tmp
    Affected if An rMake chroot environment exists on the system
  3. Inspect /dev/zero permissions in chroot
    Run 'ls -la <chroot_path>/dev/zero' to check file permissions and ownership
    Affected if The /dev/zero device file is readable and writable by the rMake user (not restricted to root only)
  4. Compare device numbers with /dev/port
    Run 'ls -la /dev/port' and 'ls -la <chroot_path>/dev/zero' to compare minor device numbers
    Affected if The minor device number of /dev/zero in the chroot matches the minor device number of /dev/port on the host system

A system is affected if rMake version 1.0.11 is installed with a chroot environment where /dev/zero has read/write access for the rMake user and shares the same minor device number as /dev/port.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or remove the /dev/zero device file creation in the chroot environment, or implement proper device file permission controls and avoid using matching minor device numbers with system devices.

Fix this in Rmake Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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