dbcve.org
OspreyApplication · Ibiblio

CVE-2006-6630

HIGH · 7.5 CVSS v2.0 Published 2006-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
PHP remote file inclusion vulnerability in ListRecords.php in osprey 1.0 allows remote attackers to execute arbitrary PHP code via a URL in the lib_dir parameter.

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

osprey 1.0 contains a remote file inclusion vulnerability in ListRecords.php where the lib_dir parameter is not properly validated, allowing remote attackers to specify a URL to a malicious PHP file that will be included and executed by the server.

MitigationDisable PHP's allow_url_include directive and implement strict input validation on the lib_dir parameter to restrict it to local paths only, or upgrade 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
OspreyApplication
Affected:= 1.0

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
Partial
Availability
Partial

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

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. Confirm Osprey installation
    Search for the Osprey application directory or check web server document roots for 'osprey' folder
    Affected if Osprey 1.0 is present on the server
  2. Identify ListRecords.php
    Locate ListRecords.php within the Osprey installation directory
    Affected if ListRecords.php file exists in the application
  3. Verify PHP execution environment
    Check if the web server is configured to execute PHP scripts and if PHP is installed
    Affected if PHP is enabled and processing .php files
  4. Inspect lib_dir parameter handling
    Review the ListRecords.php source code for how the lib_dir parameter is processed and whether it allows URL-based input
    Affected if The lib_dir parameter accepts external URLs without validation
  5. Check PHP configuration
    Examine PHP configuration for allow_url_include setting
    Affected if allow_url_include is enabled (makes exploitation easier but not required)

If Osprey 1.0 is installed with ListRecords.php accessible and the lib_dir parameter accepts unvalidated input, the environment is vulnerable to remote file inclusion.

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

Disable PHP's allow_url_include directive and implement strict input validation on the lib_dir parameter to restrict it to local paths only, or upgrade to a patched version if available.

Fix this in Osprey Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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