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

[GHSA-f626-677r-j5vq] Nette Database SQL injection #5079

Open
wants to merge 1 commit into
base: CSIRTTrizna/advisory-improvement-5079
Choose a base branch
from

Conversation

CSIRTTrizna
Copy link

Updates

  • Affected products
  • References

Comments
The vulnerability has been disputed and the resources are no longer available

@github-actions github-actions bot changed the base branch from main to CSIRTTrizna/advisory-improvement-5079 December 12, 2024 10:54
@darakian
Copy link
Contributor

and the resources are no longer available

This resource?
https://github.com/CSIRTTrizna/CVE-2024-55586

This is a repo under your account is it not?

@CSIRTTrizna
Copy link
Author

Used to be yes, however the vulnerability has been disputed and the repository has been made private as a result.

@darakian
Copy link
Contributor

darakian commented Dec 13, 2024

the repo was private before the cve was disputed though. See: #5074 (comment)
Note the time of my comment and the history on the nvd page.

The other link has thankfully been captured by the wayback machine
https://web.archive.org/web/20241211070016/https://www.csirt.sk/nette-framework-vulnerability-permits-sql-injection.html
But with both primary source links now being dead it seems to me that this CVE should really be rejected. Are you the one that requested the cve from mitre? If so please ask them to reject it unless you believe it to be a valid issue and if you believe it to be a valid issue then open up your repo and lets have a conversation 👍

@sheriffjimmy
Copy link

@CSIRTTrizna I think that it would be more professional to inform about the fact that reported vulnerability was a false positive instead of removing the article and making your repo private.

@darakian
Copy link
Contributor

@CSIRTTrizna I'd like to get this resolved. Can you comment on how you intend to move forward here?

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

Successfully merging this pull request may close these issues.

3 participants