CVE-2013-2582
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 redirect servlet in Open-Xchange AppSuite and Server before 6.22.0 rev15, 6.22.1 before rev17, 7.0.1 before rev6, and 7.0.2 before rev7 allows remote attackers to inject arbitrary HTTP headers and conduct open redirect attacks by leveraging improper sanitization of whitespace characters.
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 Open-Xchange AppSuite/Server redirect servlet allows attackers to inject arbitrary HTTP headers and conduct open redirect attacks by exploiting improper sanitization of whitespace characters.
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.22.0= 6.22.1= 7.0.1= 7.0.2= 6.22.0= 6.22.1= 7.0.1= 7.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 Open-Xchange installation and versionRun 'rpm -qa | grep -i open-xchange' or check the package management system for installed Open-Xchange packages. Alternatively, query the oxadm CLI if available: 'oxadm get version'Affected if The installed version matches 6.22.0, 6.22.1, 7.0.1, or 7.0.2
-
Locate the redirect servlet configurationSearch for servlet configuration files in the Tomcat or servlet container deployment directory. Typical path patterns: /opt/open-xchange/etc/servlet*.xml or within the OX app suite web.xml. Also check /var/log/open-xchange for startup logs mentioning 'redirect' servlet.Affected if A redirect servlet is configured and deployed in the Open-Xchange web application
-
Verify redirect servlet is accessibleTest accessing the redirect endpoint. Common paths: /redirect or /oxd/redirect. Check web.xml for servlet mappings under <url-pattern>. Also examine the Apache or Tomcat proxy configuration for routes exposing the redirect functionality.Affected if The redirect servlet is mapped and accessible via HTTP
-
Inspect redirect servlet for whitespace sanitizationExamine the redirect servlet source code or decompiled class if accessible. Look for input validation on the 'url' or 'redirect' parameter. Check if whitespace characters (\r, \n, space, tab) are being filtered before using the parameter in HTTP header construction or redirect operations.Affected if The servlet does not properly sanitize whitespace characters from redirect parameters, allowing CRLF injection or open redirect
You are affected if Open-Xchange version 6.22.0, 6.22.1, 7.0.1, or 7.0.2 is installed AND the redirect servlet is enabled with missing whitespace character sanitization.
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 versions (6.22.0 rev15, 6.22.1 rev17, 7.0.1 rev6, 7.0.2 rev7 or later) or implement proper whitespace character sanitization in the redirect servlet.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2582 — 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-2013-2582 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