Skip to content

Example Gemfile.lock raising AWS Inspector vulnerabilities #393

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

Open
matthewtusker opened this issue Feb 18, 2025 · 4 comments
Open

Example Gemfile.lock raising AWS Inspector vulnerabilities #393

matthewtusker opened this issue Feb 18, 2025 · 4 comments

Comments

@matthewtusker
Copy link

The example Gemfile.lock is raising up as an error in AWS Inspector. The file is found inside one of our Docker images, which causes it to panic that a bunch of vulnerabilities exist, when of course they don't.

Can this file be updated/removed?

@matthewtusker
Copy link
Author

It's just occurred to me that the file doesn't need to be edited at all, it just needs to be excluded in the gemspec.

@aussiDavid
Copy link
Contributor

Does #392 resolve the issue?

@matthewtusker
Copy link
Author

I think it probably does, but I haven't been able to check it. If I find time I'll test with master. We've possibly already got an exclusion added to AWS Inspector to ignore this file, so not sure if it will flag up now either way. It would be better to just exclude the file from the Gem, which would avoid this triggering again in the future.

@aussiDavid
Copy link
Contributor

aussiDavid commented Apr 15, 2025

Thanks @matthewtusker. That's a good idea. I've created a PR #394 to exclude the example/ directory. My workplace is strongly against adding exclusions in AWS Inspector, so I'm left with updating dependencies.

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

2 participants