Bug 181802 - scripts/services/http lists false positive "exploit" on any URL with "null" in it
scripts/services/http lists false positive "exploit" on any URL with "null" i...
Product: Fedora
Classification: Fedora
Component: logwatch (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ivana Varekova
Depends On:
  Show dependency treegraph
Reported: 2006-02-16 13:19 EST by Gilbert E. Detillieux
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-20 03:47:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to fix false positive probe matches on "null" (339 bytes, patch)
2006-02-16 13:19 EST, Gilbert E. Detillieux
no flags Details | Diff

  None (edit)
Description Gilbert E. Detillieux 2006-02-16 13:19:10 EST
Description of problem:
The logwatch report on the http service incorrectly includes some
valid request URL's (under the 'possible successful probes' heading) if those
log entries have the substring "null" anywhere in the quoted request field.
For example:
 !!!! 1 possible successful probes 
    /horde3/themes/graphics/tree/nullonly.png HTTP Response 200 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Produce access_log entries with GET request containing "null" in a valid URL
2.Run: logwatch --service http
3.Note incorrectly flagged "probe" in report.
Actual results:
Report includes requests that should be considered valid otherwise.

Expected results:
Such requests should not be included in the report. The match should be made
more explicit, e.g. to match URL's ending in "null" only.

Additional info:
Patch to follow.
Comment 1 Gilbert E. Detillieux 2006-02-16 13:19:11 EST
Created attachment 124770 [details]
patch to fix false positive probe matches on "null"
Comment 2 Ivana Varekova 2006-02-20 03:47:37 EST
Thank you for your notice. This problem is fixed in the last version
(logwatch-7.1-8). The result consists of string ^null$ which describes just the
possible exploit. 

Note You need to log in before you can comment on or make changes to this bug.