Empower
- Known vulnerabilities
- 0
- Still open
- 0
- KEV open
- 0
- Max CVSS (historical)
- —
Cumulative exposure
Low
Aggregates open CVEs (40%) + KEV (30%) + critical shared permissions (15%) + trackers (10%) + OS EOL (5%). Higher score = more exposed.
-
Open CVEs +0/+50
0 open CVEs, max CVSS 0.0, EPSS 0%
-
Active KEVs +0/+35
0 CISA KEVs still open
-
Permissions +0/+10
0 critical shared permission(s)
-
Trackers +0/+8
0 identification/profiling tracker(s)
-
EOL OS +0/+5
Installed OS is end-of-life
Based on permissions only: no CVE data referenced for this app.
Known vulnerabilities (CVE)
No CVE is currently referenced in NVD for this app on its platform.
The absence of CVEs is not a security guarantee — it can also mean nobody has audited or published findings.
Context
Context
Description
We started Empower to help drivers who can’t make a sustainable living under the current rideshare model and to facilitate an alternative for passengers who want the convenience provided by on-demand transportation platforms, but prefer to support companies that have high ethical standards and treat all people with respect. Through our P2P SaaS, Empower is achieving these goals and enabling passengers to obtain less expensive and more customized transportation directly from drivers.
Data collected and shared
Source: App Store · App Privacy · 6 data item(s) declared
Indicative classification based on data sensitivity. "Shared" = transmitted to third parties (publisher-declared).
FAQ
FAQ: Empower
Why are no CVEs listed for Empower?
No CVE is currently referenced in NVD for Empower (com.yazam.passenger) with a iOS CPE configuration. Either none has been publicly disclosed, or none has been mapped yet. Absence of a CVE is not a security guarantee.
What is the latest known version of Empower?
The most recent version of Empower (com.yazam.passenger) tracked by Appaloosa Scout is 2.14.2, published by YAZAM INC..