Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a limit on number of sessions a user can have #10183

Open
samczsun opened this issue Mar 7, 2025 · 1 comment
Open

Add a limit on number of sessions a user can have #10183

samczsun opened this issue Mar 7, 2025 · 1 comment
Labels
bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team

Comments

@samczsun
Copy link

samczsun commented Mar 7, 2025

Description

Each session takes up some memory in Redis, a user (or misbehaving service account) can easily eat up all the memory on the server by mass-creating sessions. It's a simple thing to fix, but it would be nice if a misconfigured account didn't have the ability to nuke the entire instance

Environment

  1. OS (where OpenCTI server runs): Linux
  2. OpenCTI version: 6.4.11
  3. OpenCTI client: N/A
  4. Other environment details:

Reproducible Steps

  1. Create a lot of sessions
  2. Redis OOM

Expected Output

Redis doesn't OOM

Actual Output

Redis OOM

Additional information

Screenshots (optional)

@samczsun samczsun added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 7, 2025
@richard-julien
Copy link
Member

This #8877 that will be available in the 6.6 to comes will I think solve your problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team
Projects
None yet
Development

No branches or pull requests

2 participants