CVE-2006-6699
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 · uneditedMultiple CRLF injection vulnerabilities in Oracle Portal 9.0.2 and possibly other versions allow remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the enc parameter to (1) calendarDialog.jsp or (2) fred.jsp. NOTE: the calendar.jsp vector is covered by CVE-2006-6697.
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 confidenceOracle Portal 9.0.2 contains CRLF injection vulnerabilities in calendarDialog.jsp and fred.jsp. The 'enc' parameter fails to sanitize CRLF sequences, allowing remote attackers to inject arbitrary HTTP headers and perform HTTP response splitting attacks.
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= 9.0.2CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 Oracle Portal installationLocate Oracle Application Server Portal installation directory and check version information in ORACLE_HOME/portal/conf or via Oracle Enterprise ManagerAffected if Version is exactly 9.0.2
-
Locate vulnerable JSP filesSearch for calendarDialog.jsp and fred.jsp in the portal web document root (typically under ORACLE_HOME/portal/webapps/portal/ or similar path)Affected if Either calendarDialog.jsp or fred.jsp exists in the portal deployment
-
Verify portal is network accessibleCheck if the portal HTTP listener is bound to a network interface and accessible from outside localhostAffected if Portal is exposed on a reachable network address
-
Test enc parameter for CRLF injectionSend HTTP request to calendarDialog.jsp or fred.jsp with enc parameter containing CRLF sequences (e.g., enc=test%0D%0AHeader:value) and observe if headers are injected into responseAffected if Application accepts and reflects unsanitized CRLF in the enc parameter
If Oracle Application Server Portal 9.0.2 is running with the vulnerable JSP files (calendarDialog.jsp or fred.jsp) accessible on the network, the environment 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 dataApply Oracle security patches for this vulnerability. If patches are unavailable, implement input validation to reject or sanitize CRLF sequences in the 'enc' parameter, or consider upgrading to a supported Oracle Portal version.
- 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-2006-6699 — 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-2006-6699 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