CVE-2013-7373

Description

Android before 4.4 does not properly arrange for seeding of the OpenSSL PRNG, which makes it easier for attackers to defeat cryptographic protection mechanisms by leveraging use of the PRNG within multiple applications.

Category

7.5
CVSS
Severity: High
CVSS 2.0 •
EPSS 0.23%
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://marc.info/?l=openssl-dev&m=130298304903422&w=2 mailing list
http://emboss.github.io/blog/2013/08/21/openssl-prng-is-not-really-fork-safe/
http://android-developers.blogspot.com.au/2013/08/some-securerandom-thoughts.html
http://www.reddit.com/r/Android/comments/1k6f03/due_to_a_serious_encryptionrng_flaw_in_android/cblvum5
http://marc.info/?l=openssl-dev&m=130289811108150&w=2 mailing list

Frequently Asked Questions

What is the severity of CVE-2013-7373?
CVE-2013-7373 has been scored as a high severity vulnerability.
How to fix CVE-2013-7373?
To fix CVE-2013-7373, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2013-7373 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2013-7373 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.