CVE-2009-0868
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 · uneditedCRLF injection vulnerability in the WebLink template in Fujitsu Jasmine2000 Enterprise Edition allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified vectors.
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 confidenceCRLF injection vulnerability in the WebLink template of Fujitsu Jasmine2000 Enterprise Edition allows remote attackers to inject carriage return and line feed characters into HTTP headers, enabling HTTP response splitting attacks. This occurs due to insufficient input validation on user-supplied data that gets incorporated into HTTP responses.
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 dataall versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 if Fujitsu Jasmine2000 is installedSearch for installation directories (e.g., Program Files/Jasmine, or registry entries for Fujitsu Jasmine), check for running services named Jasmine or WebLink, or look for jasmine2000.exe processesAffected if Fujitsu Jasmine2000 Enterprise Edition software is present on the system
-
Verify WebLink component is enabledCheck if WebLink service/template is accessible via network (typically port 80/443 or configured web port), review service configuration for WebLink module statusAffected if WebLink web interface is accessible and operational
-
Inspect WebLink template configurationLocate WebLink template configuration files (look in installation directory for template, config, or web subdirectories), examine XML or configuration files for user input fields that map to HTTP headersAffected if WebLink templates accept user-supplied input without CRLF filtering
-
Test for CRLF injection vulnerabilitySend HTTP requests to WebLink endpoints with CR/LF characters (%0D%0A) in parameter values (e.g., query strings, form inputs), observe if injected characters appear in response headersAffected if Injected CRLF sequences appear in HTTP response headers or split responses are returned
-
Review HTTP response headersCapture and inspect raw HTTP responses from WebLink, look for unexpected headers or evidence of response splitting (multiple status lines or headers)Affected if HTTP responses contain unexpected headers or show signs of response splitting
If Fujitsu Jasmine2000 Enterprise Edition with WebLink is installed and the web interface accepts user input that appears unsanitized in HTTP headers, the system is affected by this CRLF injection vulnerability.
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 dataImplement strict input validation to filter or escape CRLF characters (\r\n) from all user-controlled data before including it in HTTP headers. Apply output encoding appropriate for the HTTP header context.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0868 — 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-2009-0868 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