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 in SQLite3.39.2 CVE-2024-0232 #641

Closed
sankar-gp opened this issue Jan 30, 2024 · 5 comments
Closed

Vulnerability in SQLite3.39.2 CVE-2024-0232 #641

sankar-gp opened this issue Jan 30, 2024 · 5 comments

Comments

@sankar-gp
Copy link

Our internal tool reported that there is a Vulnerability in SQLite3.39.2

CVE-2024-0232

A heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service.

@developernotes
Copy link
Member

Hello @sankar-gp,

This issue was addressed in SQLite upstream 3.43.2. The latest SQLCipher release, 4.5.6 is based on SQLite upstream 3.44.2. Please note that we stopped releasing Community builds of android-database-sqlcipher with 4.5.4 which is based on SQLite upstream 3.41.2. Our long-term supported replacement for android-database-sqlcipher is sqlcipher-android. If you are a Commercial customer using android-database-sqlcipher, please feel free to reach out directly at support@zetetic.net.

@sankar-gp
Copy link
Author

Does this issue Vulnerability our application?

@developernotes
Copy link
Member

Hi @sankar-gp,

If your application is using SQLite 3.39.2, via SQLCipher 4.5.2 we would recommend you update your library.

@sankar-gp
Copy link
Author

sankar-gp commented Jan 31, 2024

We are using 'net.zetetic:android-database-sqlcipher:4.5.3@aar' and 'net.zetetic:android-database-sqlcipher:4.5.4@aar' versions in our app

@sjlombardo
Copy link
Member

@sankar-gp - it appears you have cross-posted this issue in several places, please reference our response to your question on the SQLCipher Discussion Site.

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

3 participants