dbcve.org
Sql LedgerWeb browser

CVE-2007-1541

HIGH · 7.5 CVSS v2.0 Published 2007-03-20
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
Directory traversal vulnerability in am.pl in SQL-Ledger 2.6.27 only checks for the presence of a NULL (%00) character to protect against directory traversal attacks, which allows remote attackers to run arbitrary executables and bypass authentication via a .. (dot dot) sequence in the login 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

The am.pl script in SQL-Ledger 2.6.27 contains a flawed directory traversal protection mechanism that only checks for NULL (%00) characters but fails to filter or validate '..' (dot-dot) sequences in the login parameter. This allows remote attackers to bypass authentication and potentially execute arbitrary commands on the server.

MitigationUpgrade SQL-Ledger to a version that properly validates all path traversal sequences (not just NULL bytes) and implements robust input sanitization for the login parameter. If upgrade is not possible, implement web application firewall rules to block directory traversal patterns.

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
Sql LedgerWeb browser
Affected:= 2.6.27

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. Identify if SQL-Ledger is installed
    Search the system for SQL-Ledger files, typically located in web server directories such as /usr/lib/cgi-bin/sql-ledger, /var/www/sql-ledger, or similar paths depending on the operating system and web server configuration.
    Affected if SQL-Ledger software is found on the system
  2. Determine the installed SQL-Ledger version
    Locate the version file or check the am.pl script header for the version string, commonly found in the same directory as the SQL-Ledger CGI scripts.
    Affected if The installed version matches 2.6.27 exactly
  3. Verify the am.pl script exists
    Find the am.pl script in the SQL-Ledger CGI directory (commonly named am.pl or Am.pl), which contains the login parameter handling code.
    Affected if The am.pl script is present in the SQL-Ledger installation
  4. Inspect the login parameter handling in am.pl
    Open am.pl and search for the login parameter processing code. Check if the validation logic only contains a filter for NULL bytes (%00) but lacks filtering for dot-dot sequences (..). Look for patterns like 's/%00//g' or similar NULL byte removal without '..' sequence blocking.
    Affected if The code shows NULL byte filtering but no '..' sequence validation in the login parameter handling
  5. Confirm web accessibility of the vulnerable script
    Check if the web server is configured to execute am.pl as a CGI script and is accessible via HTTP/HTTPS requests, typically at paths like /cgi-bin/am.pl or /am.pl.
    Affected if The am.pl script is accessible over the network through the web server

You are affected if SQL-Ledger version 2.6.27 is installed with the am.pl script accessible over the web and the login parameter only filters NULL bytes without blocking directory traversal sequences.

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 SQL-Ledger to a version that properly validates all path traversal sequences (not just NULL bytes) and implements robust input sanitization for the login parameter. If upgrade is not possible, implement web application firewall rules to block directory traversal patterns.

Fix this in Sql Ledger Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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