diff options
| author | Jeff Sharkey <jsharkey@android.com> | 2019-07-17 18:54:49 -0600 |
|---|---|---|
| committer | Max Spector <mspector@google.com> | 2019-09-18 17:13:22 -0700 |
| commit | 1730e9b26321596c6c47de00cca3b88b9948d38e (patch) | |
| tree | 5989f28139d5b847122875749aee37c69121adfb /res/values-vi/cm_plurals.xml | |
| parent | dea9d8bdec120fb1e1fa44561fb1215034fba48f (diff) | |
| download | android_packages_providers_DownloadProvider-1730e9b26321596c6c47de00cca3b88b9948d38e.tar.gz android_packages_providers_DownloadProvider-1730e9b26321596c6c47de00cca3b88b9948d38e.tar.bz2 android_packages_providers_DownloadProvider-1730e9b26321596c6c47de00cca3b88b9948d38e.zip | |
RESTRICT AUTOMERGE
Enable stricter SQLiteQueryBuilder options.
Malicious callers can leak side-channel information by using
subqueries in any untrusted inputs where SQLite allows "expr" values.
This change starts using setStrictColumns() and setStrictGrammar()
on SQLiteQueryBuilder to block this class of attacks. This means we
now need to define the projection mapping of valid columns, which
consists of both the columns defined in the public API and columns
read internally by DownloadInfo.Reader.
We're okay growing sAppReadableColumnsSet like this, since we're
relying on our trusted WHERE clause to filter away any rows that
don't belong to the calling UID.
Remove the legacy Lexer code, since we're now internally relying on
the robust and well-tested SQLiteTokenizer logic.
Bug: 135270103
Bug: 135269143
Test: cts-tradefed run cts -m CtsAppTestCases -t android.app.cts.DownloadManagerTest
Change-Id: I302091ceda3591785b2124575e89dad19bc97469
(cherry picked from commit a9533dcd628fc8f83e9cf948fc4ca09c2d139e2b)
Diffstat (limited to 'res/values-vi/cm_plurals.xml')
0 files changed, 0 insertions, 0 deletions