Ipear

Vendor:

First CVE: Jul 14, 2020 · Active for 6 years

1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
5.4
Avg CVSS
Higher Avg CVSS than 11% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Ipear over time

Volume of CVEsAvg CVSS Base Score
First CVE
Jul 14, 2020
6 years ago
Most Recent CVE
Jul 14, 2020
2,202 days ago

CVE Severity & Scoring

Ipear1 CVEs
All CVEs352,427 CVEs
Medium
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None1 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low1 (100.0%)
High0 (0.0%)
None0 (0.0%)
Unknown0 (0.0%)

Top CVEs

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

1 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
In iPear, the manual execution of the eval() function can lead to command injection. Only PCs where commands are manually executed via "For Developers" are affected. This function
Jul 14, 20205.416NONO

Exploit Exposure

Signals from CVEs in this product scope (1 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 (1 CVEs).

Media Mentions

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

Top CNAs Publishing CVEs For Ipear

Top CWEs

Versions

VersionCVE CountAvg CVSSAvg EPSSKEVExploits
0.7.015.41.4%00
0.6.1515.41.4%00
0.6.1415.41.4%00