CVE-2007-0792
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 · uneditedThe mod_perl initialization script in Bugzilla 2.23.3 does not set the Bugzilla Apache configuration to allow .htaccess permissions to override file permissions, which allows remote attackers to obtain the database username and password via a direct request for the localconfig file.
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 confidenceThe mod_perl initialization script in Bugzilla 2.23.3 fails to configure Apache to allow .htaccess files to override file permissions, enabling remote attackers to directly request and obtain the localconfig file containing plaintext database credentials.
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= 2.23.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Bugzilla versionCheck the version.pl or Bugzilla/Config.pm file in the Bugzilla installation directory. Look for the version number in the installed files.Affected if The installed version is exactly 2.23.3
-
Locate the localconfig fileFind the localconfig file in the Bugzilla directory (typically localconfig or localconfig.pl in the Bugzilla root). Verify its full filesystem path.Affected if The localconfig file exists within the web-accessible document root directory
-
Verify web server configuration for AllowOverrideCheck the Apache configuration file (httpd.conf or included configuration files) for the directory block corresponding to the Bugzilla web root. Look for the AllowOverride directive.Affected if AllowOverride is set to None or does not include 'FileInfo' and 'Limit' options, preventing .htaccess from being processed
-
Check for .htaccess file in Bugzilla directoryLook for a .htaccess file in the Bugzilla web-accessible directory. Inspect its contents to see if it restricts access to localconfig files.Affected if No .htaccess file exists, or the existing .htaccess does not block access to the localconfig file
-
Test direct HTTP request to localconfigAttempt to request the localconfig file via HTTP (e.g., http://yourserver/bugzilla/localconfig) using a web browser or curl command.Affected if The server returns the contents of the localconfig file instead of denying access
You are affected if you are running Bugzilla version 2.23.3 and the localconfig file is web-accessible without .htaccess protection enabled via AllowOverride.
Generated from the published advisory. Verify against your own configuration.
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 dataConfigure Apache with 'AllowOverride All' to enable .htaccess protections, or move the localconfig file outside the web-accessible directory tree and update Bugzilla to reference the new path.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2007-0792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0792 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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