diff options
| author | Jonatan Rhodin <jonatan.rhodin@mullvad.net> | 2023-12-06 23:31:53 +0100 |
|---|---|---|
| committer | Jonatan Rhodin <jonatan.rhodin@mullvad.net> | 2023-12-06 23:31:53 +0100 |
| commit | bc20099e5e8a68aecbb53afdca4132b2972045dc (patch) | |
| tree | cc2256946413bba283807396c36ffc6c6dab8d52 /android | |
| parent | 1de1978fc98fad3d1d7bb5086c8757aab4ed2155 (diff) | |
| parent | eb7edafec223280d717772ae92f7573bb232e4ac (diff) | |
| download | mullvadvpn-bc20099e5e8a68aecbb53afdca4132b2972045dc.tar.xz mullvadvpn-bc20099e5e8a68aecbb53afdca4132b2972045dc.zip | |
Merge branch 'address-expired-suppression-of-cve-2023-3635-droid-562'
Diffstat (limited to 'android')
| -rw-r--r-- | android/config/dependency-check-suppression.xml | 2 | ||||
| -rw-r--r-- | android/test/test-suppression.xml | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/android/config/dependency-check-suppression.xml b/android/config/dependency-check-suppression.xml index 57e19a9d54..067a8c8d67 100644 --- a/android/config/dependency-check-suppression.xml +++ b/android/config/dependency-check-suppression.xml @@ -41,7 +41,7 @@ <packageUrl regex="true">^pkg:maven/org\.jetbrains\.kotlin/kotlin\-stdlib.*@.*$</packageUrl> <cve>CVE-2022-24329</cve> </suppress> - <suppress until="2023-12-01Z"> + <suppress until="2024-06-01Z"> <notes><![CDATA[ This CVE only affect the leakCanary build type which is limited to memory leak testing etc. This will most likely be solved by bumping to a future version of the leakcanary dependency diff --git a/android/test/test-suppression.xml b/android/test/test-suppression.xml index 720ef7d197..f92e67c0db 100644 --- a/android/test/test-suppression.xml +++ b/android/test/test-suppression.xml @@ -92,7 +92,7 @@ <packageUrl regex="true">^pkg:maven/com\.android\.tools/common@.*$</packageUrl> <cve>CVE-2021-4277</cve> </suppress> - <suppress until="2023-12-01Z"> + <suppress until="2024-06-01Z"> <notes><![CDATA[ This CVE only affect the leakCanary build type which is limited to memory leak testing etc. This will most likely be solved by bumping to a future version of the leakcanary dependency |