CVE-2008-1167
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 · uneditedStack-based buffer overflow in the useragent function in useragent.c in Squid Analysis Report Generator (Sarg) 2.2.3.1 allows remote attackers to execute arbitrary code via a long Squid proxy server User-Agent header. NOTE: some of these details are obtained from third party information.
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 confidenceStack-based buffer overflow in Sarg's useragent function when processing Squid proxy logs. The User-Agent header from proxy logs is copied into a fixed-size buffer without proper bounds checking, allowing remote attackers to overwrite stack memory and execute arbitrary code by sending unusually long User-Agent strings through the Squid proxy.
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.2.3.1CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 if Sarg is installedRun 'sarg -v' or 'sarg --version' to display the installed Sarg version. Alternatively, check your package manager (e.g., 'dpkg -l | grep sarg' or 'rpm -qa | grep sarg').Affected if The installed version is 2.2.3.1 exactly.
-
Verify the exact Sarg versionCompare the version output from the previous step against the affected version 2.2.3.1. Sarg versions prior to 2.2.3.1 and later patched versions are not affected by this specific CVE.Affected if The version shown is precisely 2.2.3.1.
-
Check if Sarg processes Squid proxy logsExamine the Sarg configuration file (typically /etc/sarg/sarg.conf or /etc/sarg.conf) for directives that process Squid access logs, such as 'access_log' pointing to your Squid log file.Affected if Sarg is configured to read Squid access logs that contain User-Agent header data.
-
Confirm useragent processing is enabledLook in the Sarg configuration for settings related to user agent reporting, such as 'useragent' directive or sections that enable User-Agent field extraction from Squid logs.Affected if User-Agent processing or useragent reporting is explicitly enabled in the configuration.
-
Identify if Sarg is run against live or archived Squid logsReview cron jobs, scripts, or automation that execute Sarg (typically via 'sarg' command) and identify which Squid log files it processes.Affected if Sarg is executed against Squid logs containing User-Agent headers from proxy requests.
You are affected if Sarg version 2.2.3.1 is installed AND it is configured to process Squid proxy logs with User-Agent header data enabled.
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 dataUpgrade to patched Sarg version; alternatively, implement input validation to limit User-Agent header length before Sarg processes logs, or filter/block excessively long User-Agent headers at the proxy level.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1167 — 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-2008-1167 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