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

Vulnerability to CVE-2018-12684 #81

Open
CharlyReux opened this issue Jan 10, 2025 · 1 comment
Open

Vulnerability to CVE-2018-12684 #81

CharlyReux opened this issue Jan 10, 2025 · 1 comment

Comments

@CharlyReux
Copy link

CharlyReux commented Jan 10, 2025

Hi, great project!

As part of a research experiment, we developed a tool that allows us to crawl through existing vulnerabilities in upstream projects, that are potentially not fixed in fork.
We have a suspicion that your repository, which shares commits withhttps://github.com/civetweb/civetweb is still vulnerable to CVE-2018-12684

The vulnerability has been fixed upstream via this commit civetweb/civetweb@8fd069f

However, we could not find the patch applied in this repository

if ( ! memcmp( buf + 5, "include", 7 ) ) {

If possible, we would like to know whether it is indeed vulnerable to the vulnerability we described.

Your insight would be very valuable for our experiment.
Do not hesitate to contact us if you want more information.
Thanks again.

@lammertb
Copy link
Owner

Thanks for bringing this up.
The source file indeed contains the unpatched code.
I will apply the patch mentioned in CVE-2018-12684

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