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

CVE-2021-40978 - Path Traversal. #2601

Closed
farinap5 opened this issue Oct 8, 2021 · 7 comments · Fixed by #2604
Closed

CVE-2021-40978 - Path Traversal. #2601

farinap5 opened this issue Oct 8, 2021 · 7 comments · Fixed by #2604

Comments

@farinap5
Copy link

farinap5 commented Oct 8, 2021

Hey!

We have verified a security flaw in the current version of MKdocs, a path traversal failure affecting the built-in dev-server.

That flaw turns the server susceptible to providing data outside the scope of the application allowing anyone to request sensitive files.

If you need further information, don't hesitate to get in touch with me.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40978
https://github.com/nisdn/CVE-2021-40978

@facelessuser
Copy link
Contributor

It should be mentioned the dev server is known to not be secure and should not be used in a sensitive environment. The security flaw is using the dev-server in an unsafe way, e.g., as a public server and not just as a development server.

@oprypin
Copy link
Contributor

oprypin commented Oct 10, 2021

Thanks for the report. Perhaps you could try out with the fix in #2604.

@LFKoning
Copy link

LFKoning commented Nov 8, 2023

Hi @oprypin,

Stumbled upon this issue after using pip-audit; seems this vulnerability was fixed in 1.2.3 (#2604), but unfortunately it is still listed as active in the PyPA vulnerability advisory-database: https://github.com/pypa/advisory-database/blob/main/vulns/mkdocs/PYSEC-2021-878.yaml. Is there any way to correct that information?

Cheers!

@oprypin
Copy link
Contributor

oprypin commented Nov 8, 2023

@LFKoning thanks for bringing this up. I don't know, your guess is as good as mine. Maybe someone would need to suggest an edit in the repository that you linked? Could you try to search around?

@oprypin
Copy link
Contributor

oprypin commented Nov 8, 2023

That file is a mess.. the only versions are 1.2, 1.2.1, 1.2.2
but it lists every version that ever existed 😂

@LFKoning
Copy link

LFKoning commented Nov 8, 2023

@oprypin thanks for the replies.

And yeah.. It's not pretty. I'll search around if anything can be done about it. Seems like that database is compiled from yet another database...

I'll report back here if I have more info.

@andreportela
Copy link

Any news on this?

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 a pull request may close this issue.

5 participants