Diary With Lock

Vendor:

First CVE: Oct 27, 2017 · Active for 8 years

2
Total CVEs
More Total CVEs than 49% of tracked products
2.0
Avg CVEs / Year
Higher CVE frequency than 60% of tracked products
7.5
Avg CVSS
Higher Avg CVSS than 50% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Diary With Lock over time

Volume of CVEsAvg CVSS Base Score
First CVE
Oct 27, 2017
8 years ago
Most Recent CVE
Oct 27, 2017
3,195 days ago

CVE Severity & Scoring

Diary With Lock2 CVEs
All CVEs352,727 CVEs
High
Attack Vector
Local0 (0.0%)
Network2 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low2 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None2 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None2 (100.0%)
Unknown0 (0.0%)

Top CVEs

Signals from CVEs in this product scope (2 CVEs).

2 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
In net.MCrypt in the "Diary with lock" (aka WriteDiary) application 4.72 for Android, hardcoded SecretKey and iv variables are used for the AES parameters, which makes it easier fo
Oct 27, 20177.523NONO
In the "Diary with lock" (aka WriteDiary) application 4.72 for Android, neither HTTPS nor other encryption is used for transmitting data, despite the documentation that the product
Oct 27, 20177.523NONO

Exploit Exposure

Signals from CVEs in this product scope (2 CVEs).

CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%

Social Chatter

Signals from CVEs in this product scope (2 CVEs).

Media Mentions

Signals from CVEs in this product scope (2 CVEs).

Top CNAs Publishing CVEs For Diary With Lock

Top CWEs

Versions

VersionCVE CountAvg CVSSAvg EPSSKEVExploits
4.7227.51.0%00