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

Which commit fixes CVE-2023-32697? #909

Closed
pgrt opened this issue May 24, 2023 · 3 comments
Closed

Which commit fixes CVE-2023-32697? #909

pgrt opened this issue May 24, 2023 · 3 comments
Labels
question Further information is requested

Comments

@pgrt
Copy link

pgrt commented May 24, 2023

Hello,

I am the Debian maintainer of sqlite-jdbc, and I would like to fix CVE-2023-32697 in Debian.

Still, we are very close to the release of Debian 12 and it is not possible to upload Version 3.41.2.2, I can only cherry-pick some commits so that changes to the Debian-packaged software remain small.

I feel that commit edb4b8a is the one that fixes CVE-2023-32697, do you confirm? Is it enough if I cherry-pick this only commit?

Thanks a lot for your help,

Best,

--
Pierre

@pgrt pgrt added the triage label May 24, 2023
@gotson gotson added question Further information is requested and removed triage labels May 25, 2023
@pgrt
Copy link
Author

pgrt commented May 27, 2023

Hi again,

Forgive me for writing again quite quickly, but I feel it is really important to be able to fix the CVE in Debian, while packaging a new upstream version of sqlite-jdbc is unfeasible as we release Debian 12 in less than 2 weeks.

If you had the opportunity to point me to the commit(s) which fix(es) CVE-2023-32697, it would be really super useful.

Cheers,
Pierre

@Willena
Copy link
Contributor

Willena commented Jun 19, 2023

@pgrt
Copy link
Author

pgrt commented Jun 23, 2023

Hi @Willena,

Thanks for considering my questions. Still, I was concerned about the precise commit as I was willing to backport only this change in an environment in which changing the whole version was too important as a change.
Still, I am confident commit edb4b8a is the one I was looking for, some colleagues also do. Thus I picked it and I am ok with this situation.

Best,
Pierre

@pgrt pgrt closed this as completed Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants