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

[Security] Integer overflow in src/mdc2dgst_plug.c #5373

Open
the-Chain-Warden-thresh opened this issue Oct 31, 2023 · 1 comment
Open

[Security] Integer overflow in src/mdc2dgst_plug.c #5373

the-Chain-Warden-thresh opened this issue Oct 31, 2023 · 1 comment

Comments

@the-Chain-Warden-thresh
Copy link

the-Chain-Warden-thresh commented Oct 31, 2023

I've found that the code snippet in int JtR_MDC2_Update(JtR_MDC2_CTX *c, const unsigned char *in, size_t len) is quite familiar with the vulnerable code snippet in CVE-2016-6303, which will cause an integer overflow and then result in a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors.

@solardiz
Copy link
Member

@the-Chain-Warden-thresh Is this part of a research project on finding embedded copies of code with previously known bugs? A paper upcoming?

This CVE description is:

Integer overflow in the MDC2_Update function in crypto/mdc2/mdc2dgst.c in OpenSSL before 1.1.0 allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors.

We may look into updating to newer upstream code (or switch to calling into OpenSSL when available, why do we even have a copy of the code?), but I think this has no impact (let alone security impact) in JtR since the inputs are candidate passwords, which in JtR are of limited length (currently up to 125).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants