{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2013-5391 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-5391 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-5391 is a medium-severity vulnerability in n/a, published on 27 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-5391 and fix it if it is affected.\n\nWhat it is: CVE-2013-5391 is a medium-severity vulnerability in n/a, published on 27 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-5391 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2013-5391/ (Markdown: https://insights.sbomify.com/CVE-2013-5391/index.md)","id":"CVE-2013-5391","markdown":"https://insights.sbomify.com/CVE-2013-5391/index.md","name":"CVE-2013-5391","record":{"aliases":["GHSA-6r6h-3g69-3c83"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Worklight","requires_auth":"low_privilege","summary":"Attackers can defeat cryptographic protections in IBM Worklight mobile apps due to improper PRNG initialization, requiring an upgrade to secure versions.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"mobile_foundation","vendor":"ibm"},{"product":"worklight","vendor":"ibm"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2013-5391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2013"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2013-5393"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-5390"},"products":["n/a"],"published":"2018-04-27","related":[{"cvss_score":5.6,"headline":"Auth bypass in MobileFirst Platform Foundation","id":"CVE-2020-4229","kev_date_added":null,"published":"2020-06-05"},{"cvss_score":4.9,"headline":"Security feature bypass in n/a","id":"CVE-2014-0888","kev_date_added":null,"published":"2014-08-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attackers can defeat cryptographic protections in IBM Worklight mobile apps due to improper PRNG initialization, requiring an upgrade to secure versions.","url":"https://insights.sbomify.com/CVE-2013-5391/"}