Application Server PortalApplication · Oracle

CVE-2006-6697

HIGH · 7.5 CVSS v2.0 Published 2006-12-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
CRLF injection vulnerability in webapp/jsp/calendar.jsp in Oracle Portal 10g and earlier, including 9.0.2, allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the enc parameter.

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 confidence

CRLF injection vulnerability in Oracle Portal 10g and earlier allows remote attackers to inject arbitrary HTTP headers via CRLF sequences in the 'enc' parameter of webapp/jsp/calendar.jsp, enabling HTTP response splitting attacks that can lead to cache poisoning, XSS, and session hijacking.

MitigationImplement strict input validation to reject or neutralize CRLF sequences in the 'enc' parameter, or deploy a WAF to block such sequences; upgrade to a patched Oracle Portal version if available.

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
Application Server PortalApplication
Affected:= 9.0.2= 10g

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Portal installation and version
    Locate Oracle Application Server Portal installation directory and check version. On UNIX systems, common paths include $ORACLE_HOME/portal or /opt/oracle/portal. Check for version files in the installation directory or run: $ORACLE_HOME/opmn/bin/opmnctl status -l (for Oracle 10g)
    Affected if Installed version is 9.0.2 or 10g (any 10.x release)
  2. Verify calendar.jsp component exists
    Check for the existence of the vulnerable JSP file: webapp/jsp/calendar.jsp within the Oracle Portal web application directory. Common path: $ORACLE_HOME/portal/objects/portal/webapp/jsp/calendar.jsp or within the deployed EAR/WAR files
    Affected if The file webapp/jsp/calendar.jsp exists in the Oracle Portal web application directory
  3. Confirm web application is accessible
    Verify the Oracle Portal web application is running and accessible. Check if the /portal/ or /pls/ endpoints respond. Query: http://<host>:<port>/portal/ or check Oracle HTTP Server status
    Affected if Oracle Portal web application is running and accepting HTTP requests
  4. Test enc parameter for CRLF injection
    Send a test HTTP request with CRLF sequences in the 'enc' parameter. Example: GET /portal/jsp/calendar.jsp?enc=test%0D%0AHeader:+Value HTTP/1.1. Analyze response headers for evidence of injected headers or response splitting
    Affected if The application accepts and reflects CRLF sequences in the 'enc' parameter, allowing injection of arbitrary HTTP headers

If Oracle Portal version 9.0.2 or 10g is installed, the calendar.jsp component exists, and the 'enc' parameter accepts CRLF sequences, the environment is vulnerable to CVE-2006-6697.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation to reject or neutralize CRLF sequences in the 'enc' parameter, or deploy a WAF to block such sequences; upgrade to a patched Oracle Portal version if available.

Fix this in Application Server Portal Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-6697 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-6697 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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