dbcve.org
WorklightApplication · Ibm

CVE-2013-5391

MEDIUM · 5.3 CVSS v3.0 Published 2018-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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 Worklight Consumer and Enterprise Editions 5.0.x before 5.0.6 Fix Pack 2 and 6.0.x before 6.0.0 Fix Pack 2, and Mobile Foundation Consumer and Enterprise Editions 5.0.x before 5.0.6 Fix Pack 2 and 6.0.0 Fix Pack 2 make it easier for attackers to defeat cryptographic protection mechanisms by leveraging improper initialization of the pseudo random number generator (PRNG) in Android and use of the Java Cryptography Architecture (JCA) by a Worklight program. IBM X-Force ID: 87128.

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 Worklight and Mobile Foundation editions have a vulnerability where the Android platform's Pseudo Random Number Generator (PRNG) is improperly initialized, and the application makes improper use of the Java Cryptography Architecture (JCA). This results in weakened cryptographic protections, potentially allowing attackers to predict or recover cryptographic keys used by the application.

MitigationApply IBM Fix Pack 2 for version 5.0.6 or Fix Pack 2 for version 6.0.0 to address the improper PRNG initialization and JCA usage. This is a patch update that replaces the vulnerable cryptographic implementation.

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
WorklightApplication
Affected:= 5.0.0.0= 5.0.5.0= 5.0.6.0= 6.0.0.0
Mobile FoundationApplication
Affected:= 5.0.0.0= 5.0.5.0= 5.0.6.0= 6.0.0.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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 if Android platform is in use
    Determine whether your IBM Worklight or Mobile Foundation environment is being used to build, deploy, or manage Android mobile applications. Check your project configurations or application build targets for Android platform references.
    Affected if The environment builds or deploys Android applications using IBM Worklight or Mobile Foundation
  2. Check installed IBM Worklight version
    Locate the IBM Worklight installation directory and check the product version. Look for version information in the installation files, about dialog, or version metadata file. Common locations include the installation root or product-specific configuration directories.
    Affected if The installed version is 5.0.0.0, 5.0.5.0, 5.0.6.0, or 6.0.0.0
  3. Check installed IBM Mobile Foundation version
    Locate the IBM Mobile Foundation installation and verify the product version. Check the installation root directory, product metadata, or version information file for the exact version number.
    Affected if The installed version is 5.0.0.0, 5.0.5.0, 5.0.6.0, or 6.0.0.0
  4. Inspect cryptographic configuration for Android
    If accessible, examine the cryptographic configuration files or code within Android application modules built using the IBM product. Look for PRNG initialization settings and JCA configuration in the Android-specific application build or runtime configuration.
    Affected if The cryptographic implementation uses default Android PRNG without proper initialization or uses JCA incorrectly for Android platform operations

Your environment is affected if you use IBM Worklight or Mobile Foundation versions 5.0.0.0, 5.0.5.0, 5.0.6.0, or 6.0.0.0 to build or deploy Android applications with the vulnerable cryptographic implementation.

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

Apply IBM Fix Pack 2 for version 5.0.6 or Fix Pack 2 for version 6.0.0 to address the improper PRNG initialization and JCA usage. This is a patch update that replaces the vulnerable cryptographic implementation.

Fix this in Worklight Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-5391 — 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-5391 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