CVE-2008-1341
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 · uneditedSQL injection vulnerability in SearchResults.aspx in LaGarde StoreFront 6 before SP8 allows remote attackers to execute arbitrary SQL commands via the CategoryId parameter. NOTE: the provenance of this information is unknown; the details are obtained solely 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 confidenceSQL injection vulnerability in the SearchResults.aspx page of LaGarde StoreFront 6 allows remote attackers to execute arbitrary SQL commands through the CategoryId parameter without proper input sanitization, potentially enabling unauthorized data access or database compromise.
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= 6.0CVSS 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.
-
Locate StoreFront installation directoryCheck common installation paths such as C:\Inetpub\wwwroot\ or the web root directory for a folder named StoreFront or containing StoreFront files (default.aspx, web.config)Affected if StoreFront application files are present on the server
-
Identify installed StoreFront versionOpen the web.config file in the StoreFront directory and look for version information in the appSettings section, or check for a version.txt file in the application rootAffected if Version is reported as 6.0 specifically (not 6.0 SP1 through SP7)
-
Verify SearchResults.aspx existsIn the StoreFront web directory, confirm that SearchResults.aspx file is present in the root or a relevant pathAffected if SearchResults.aspx file exists in the deployed application
-
Confirm web application is accessibleAttempt to access http://[server]/StoreFront/SearchResults.aspx or the equivalent URL path to verify the page is reachable over HTTPAffected if The page responds to HTTP requests (even with an error) indicating it is exposed
-
Test CategoryId parameter behaviorSubmit a request to SearchResults.aspx with a CategoryId parameter value containing a single quote (') or a simple SQL injection test string such as ' OR '1'='1 to observe if SQL errors are returnedAffected if The application returns database error messages or behaves differently when special SQL characters are passed to CategoryId, indicating lack of input sanitization
A system is affected if it runs LaGarde StoreFront version 6.0 with the SearchResults.aspx page accessible and the CategoryId parameter accepting unsanitized input that triggers SQL syntax errors or unexpected behavior.
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 StoreFront 6 SP8 or later which contains the security patch. If immediate patching is not feasible, implement parameterized queries for the CategoryId parameter and add input validation as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1341 — 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-1341 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