# CVE-2025-50944: Security feature bypass in n/a

> AVTECH EagleEyes mobile app fails to validate TLS certificates properly, allowing attackers to bypass security checks and potentially intercept traffic.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-gg97-r299-8cpm

## What is CVE-2025-50944?

CVE-2025-50944 is a high-severity vulnerability in n/a, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in the method push.lite.avtech.com.MySSLSocketFactoryNew.checkServerTrusted in AVTECH EagleEyes 2.0.0. The custom X509TrustManager used in checkServerTrusted only checks the certificate's expiration date, skipping proper TLS chain validation.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-50944?

It affects 1 product.


Products: Avtech Eagleeyes\(lite\).

## How do I fix CVE-2025-50944?

No fix has been published for CVE-2025-50944 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-50944 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50944 exists.

Public exploit code:

- Improper Certificate Chain Validation in EagleEyes Lite Android Application (github_poc): https://github.com/shinyColumn/CVE-2025-50944

## Other vulnerabilities in n/a

- [CVE-2025-46408](https://insights.sbomify.com/CVE-2025-46408/): Security feature bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50944 and fix it if it is affected.

What it is: CVE-2025-50944 is a high-severity vulnerability in n/a, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50944 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-50944/ (Markdown: https://insights.sbomify.com/CVE-2025-50944/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-50944
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-50944
- OSV: https://osv.dev/vulnerability/CVE-2025-50944

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-50944/
Summaries are generated and may contain mistakes; the official description above is the record.