dbcve.org
Websphere CommerceApplication · Ibm

CVE-2013-2994

MEDIUM · 6.4 CVSS v2.0 Published 2013-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
IBM WebSphere Commerce 7.0 Feature Pack 4 and Feature Pack 5 incorrectly maintains a valid session after unspecified interaction with REST services, which allows remote attackers to issue REST requests in the context of an arbitrary user's active session via unknown 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 confidence

IBM WebSphere Commerce 7.0 Feature Pack 4 and 5 fails to properly invalidate user sessions after REST service interactions, allowing an attacker to issue REST requests within the context of an active user session. This session fixation/hijacking vulnerability enables remote attackers to impersonate legitimate users by exploiting improperly managed session state.

MitigationImplement proper session invalidation for REST service endpoints by configuring appropriate session timeout values and ensuring sessions are terminated after REST API calls complete.

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
Websphere CommerceApplication
Affected:= 7.0

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
None

AV:N/AC:L/Au:N/C:P/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 checks

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

  1. Identify IBM WebSphere Commerce version
    Locate the installed WebSphere Commerce version by checking the product installation directory, version manifest, or administrative console. Common locations include the versionInfo file in the installation root or through the WebSphere administrative console under Installation > Product Information.
    Affected if The installed version is IBM WebSphere Commerce 7.0 Feature Pack 4 or 5.
  2. Confirm Feature Pack installation
    Verify which Feature Packs are installed on the WebSphere Commerce environment. Check through the WebSphere administrative console or by examining the installed feature pack manifests in the Commerce installation directory.
    Affected if Feature Pack 4 or Feature Pack 5 is installed on WebSphere Commerce 7.0.
  3. Determine REST service usage
    Identify whether REST services are enabled and in use within the WebSphere Commerce environment. Review the REST service configuration files, web.xml deployment descriptors, or the REST service endpoint mappings to confirm active REST endpoints.
    Affected if REST services are enabled and accessible in the environment.
  4. Review session management configuration
    Examine the session management settings in the WebSphere Application Server administrative console or the WC_combined.xml configuration file. Look for session timeout values and session tracking configuration for REST-related URL patterns.
    Affected if Session timeout is configured but does not explicitly invalidate sessions after REST service calls complete.
  5. Check for session fixation protections
    Inspect the session configuration for evidence of proper session ID regeneration after authentication. Look for WC parameter management settings and whether new session IDs are generated when transitioning from anonymous to authenticated states in REST interactions.
    Affected if Session IDs are not regenerated after REST service authentication events, allowing session fixation.

A user is affected if they run IBM WebSphere Commerce 7.0 with Feature Pack 4 or 5, have REST services enabled, and lack proper session invalidation after REST API interactions.

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 proper session invalidation for REST service endpoints by configuring appropriate session timeout values and ensuring sessions are terminated after REST API calls complete.

Fix this in Websphere Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2013-2994 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