HeyCyan App Android Security Weaknesses

Improper access controls in the Android FileProvider component of HeyCyan App 1.0.103 allow an attacker to reach files the provider is supposed to protect, with low-rated confidentiality and integrity impact and no availability effect. The vendor was contacted about the disclosure and did not respond, and no vendor-released patch has been identified; the CVE is not listed in CISA KEV and no EPSS score was supplied, though a public PoC reference (a GitHub repository linked from the VulDB entry) exists and is not verified as working exploit code. Note that the app's own CVSS 4.0 vector claims a network attack vector (AV:N), while the independent assessment rates this as a local (AV:L) issue: the realistic path is a malicious application co-resident on the same Android device interacting with the misconfigured provider, so exposure is limited to users of this specific build who install other apps alongside it.

Cleartext transmission of sensitive information in HeyCyan App 1.0.103 on Android arises from the app's Network Security Configuration in AndroidManifest.xml, which permits non-TLS traffic that can be passively observed by anyone able to inspect the app's network path. Realistic exploitation requires the attacker to already hold a man-in-the-middle position - a hostile hotspot, ARP/DNS spoofing, or a compromised network hop - which is why the issue is rated high complexity despite needing no authentication or user interaction. Impact is confidentiality-only, the specific data exposed is not described in the available sources, and no public exploit code is confirmed; the vendor was contacted about the disclosure but did not respond, and the available signals place this below urgent priority.