dbcve.org
BaseApplication · Secureideas

CVE-2009-4592

HIGH · 7.5 CVSS v2.0 Published 2010-01-07
Fix available
A fix is available. Upgrade to after 1.4.3 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
Unspecified vulnerability in base_local_rules.php in Basic Analysis and Security Engine (BASE) before 1.4.4 allows remote attackers to include arbitrary local files via unknown vectors.

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

Local File Inclusion (LFI) vulnerability in base_local_rules.php in Basic Analysis and Security Engine (BASE) versions prior to 1.4.4 allows remote unauthenticated attackers to include arbitrary local files from the server filesystem, potentially exposing sensitive configuration data or enabling further compromise.

MitigationUpgrade to BASE version 1.4.4 or later to obtain the patched version. If immediate patching is not possible, consider deploying web application firewall rules to block directory traversal patterns (../) or temporarily restrict access to the affected script.

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
BaseApplication
Affected:<= 1.4.3= 0.9.8= 0.9.9= 1.0= 1.2.4= 1.2.5= 1.2.6= 1.2.7= 1.3.5= 1.3.6= 1.3.8= 1.3.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
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. Locate BASE installation
    Search the web server document root for directories containing 'base' or 'Basic Analysis and Security Engine' files. Common paths may include /var/www/base, /var/www/html/base, or C:\inetpub\wwwroot\base. Check for the presence of base_local_rules.php in the installation.
    Affected if The base_local_rules.php file exists in the web-accessible directory and the installed version is 1.4.3 or earlier, or matches one of the affected version numbers (0.9.8, 0.9.9, 1.0, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.3.5, 1.3.6, 1.3.8, 1.3.9).
  2. Identify installed BASE version
    Open the file base_main.php or base_include.php in the BASE directory and look for a version variable such as $base_version, BASE_VERSION, or similar. Alternatively, check for a VERSION file or CHANGELOG file in the BASE root directory that lists the version number.
    Affected if The version displayed is 1.4.3 or lower, or matches any of these specific versions: 0.9.8, 0.9.9, 1.0, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.3.5, 1.3.6, 1.3.8, or 1.3.9.
  3. Verify base_local_rules.php is web-accessible
    Confirm that base_local_rules.php is located in a directory served by the web server and is directly accessible via HTTP. Attempt to access it through a browser or curl request: http://your-server/base/base_local_rules.php
    Affected if The file returns a response (rather than a 404 error), indicating it is accessible over the network.
  4. Check if LFI is exploitable
    Attempt a benign directory traversal test by requesting a known local file through the base_local_rules.php parameter. For example: http://your-server/base/base_local_rules.php?base_path=../../etc/passwd (if the vulnerable parameter name is known). If the file contents are displayed, the vulnerability is present.
    Affected if The server returns contents of a local file that should not be accessible via the web, confirming the LFI vulnerability is exploitable.

If BASE with base_local_rules.php is installed and the version is 1.4.3 or earlier (or matches any of the listed affected versions), and the file is web-accessible, the environment is vulnerable to CVE-2009-4592.

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 1.4.3
Interim mitigation

Upgrade to BASE version 1.4.4 or later to obtain the patched version. If immediate patching is not possible, consider deploying web application firewall rules to block directory traversal patterns (../) or temporarily restrict access to the affected script.

Fix this in Base Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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