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

Access to Infected Files #1225

Open
thomasSSSC opened this issue Jun 10, 2024 · 0 comments
Open

Access to Infected Files #1225

thomasSSSC opened this issue Jun 10, 2024 · 0 comments

Comments

@thomasSSSC
Copy link

While running this scanner, I found two potential workarounds for accessing infected files:

  1. If too many objects are uploaded, and you reach the concurrent lambda limit, then files will not be tagged, and are therefore accessible. This can be fixed by changing the bucket policy to have this condition(for example):
    "Condition": {
    "StringNotEquals": {
    "s3:ExistingObjectTag/scan-status": "CLEAN"
    },
  2. Also infected files can be accessed by changing the tags on the object itself. It might be a good idea to restrict tag permissions on infected files to the root user.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant