dbcve.org
Gnump3dApplication · Gnu

CVE-2007-6130

MEDIUM · 5.0 CVSS v2.0 Published 2007-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
gnump3d 2.9final does not apply password protection to its plugins, which might allow remote attackers to bypass intended access restrictions.

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

gnump3d 2.9final fails to enforce password authentication on its plugin system, allowing remote attackers to bypass intended access restrictions and execute plugin functionality without credentials.

MitigationUpgrade to a patched version of gnump3d if available; otherwise, restrict network access to the service via firewall rules or network segmentation to limit exposure to untrusted sources.

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
Gnump3dApplication
Affected:= 2.9

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

AV:N/AC:L/Au:N/C:P/I:N/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. Identify gnump3d installation and version
    Run 'gnump3d --version' or check package manager for gnump3d package version (e.g., 'dpkg -l gnump3d' or 'rpm -qi gnump3d')
    Affected if The installed version is 2.9 or 2.9final
  2. Locate gnump3d configuration file
    Check common config locations: /etc/gnump3d.conf, /etc/gnump3d/gnump3d.conf, or ~/.gnump3d/config
    Affected if Configuration file exists and is readable
  3. Verify plugin directory exists
    Check for plugin directory (commonly /usr/share/gnump3d/plugins or /var/lib/gnump3d/plugins) and confirm it is accessible to the gnump3d process
    Affected if Plugin directory exists and is accessible without authentication
  4. Check authentication configuration in gnump3d.conf
    Search config file for 'plugin_password', 'password', 'auth' or similar settings to determine if password authentication is enforced on plugin execution
    Affected if Password authentication is not configured, disabled, or not enforced on plugin access
  5. Test remote plugin execution without credentials
    Attempt to access a known plugin URL via HTTP (e.g., http://server:port/plugin_name) without providing any authentication credentials
    Affected if Plugin executes or returns data without requiring authentication

You are affected if gnump3d version 2.9 is installed and its plugin system can be accessed or executed without password authentication.

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

Upgrade to a patched version of gnump3d if available; otherwise, restrict network access to the service via firewall rules or network segmentation to limit exposure to untrusted sources.

Fix this in Gnump3d Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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