CVE-2020-4035 (GCVE-0-2020-4035)
Vulnerability from cvelistv5 – Published: 2020-06-03 16:50 – Updated: 2024-08-04 07:52
VLAI?
Title
DoS or local data modification via malicious record IDs in WatermelonDB
Summary
In WatermelonDB (NPM package "@nozbe/watermelondb") before versions 0.15.1 and 0.16.2, a maliciously crafted record ID can exploit a SQL Injection vulnerability in iOS adapter implementation and cause the app to delete all or selected records from the database, generally causing the app to become unusable. This may happen in apps that don't validate IDs (valid IDs are `/^[a-zA-Z0-9_-.]+$/`) and use Watermelon Sync or low-level `database.adapter.destroyDeletedRecords` method. The integrity risk is low due to the fact that maliciously deleted records won't synchronize, so logout-login will restore all data, although some local changes may be lost if the malicious deletion causes the sync process to fail to proceed to push stage. No way to breach confidentiality with this vulnerability is known. Full exploitation of SQL Injection is mitigated, because it's not possible to nest an insert/update query inside a delete query in SQLite, and it's not possible to pass a semicolon-separated second query. There's also no known practicable way to breach confidentiality by selectively deleting records, because those records will not be synchronized. It's theoretically possible that selective record deletion could cause an app to behave insecurely if lack of a record is used to make security decisions by the app. This is patched in versions 0.15.1, 0.16.2, and 0.16.1-fix
Severity ?
5.9 (Medium)
CWE
- CWE-89 - Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Assigner
References
| URL | Tags | |||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Nozbe | WatermelonDB |
Affected:
< 0.15.1
Affected: >= 0.16.0, < 0.16.2 |
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-04T07:52:20.760Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"x_refsource_CONFIRM",
"x_transferred"
],
"url": "https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"product": "WatermelonDB",
"vendor": "Nozbe",
"versions": [
{
"status": "affected",
"version": "\u003c 0.15.1"
},
{
"status": "affected",
"version": "\u003e= 0.16.0, \u003c 0.16.2"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In WatermelonDB (NPM package \"@nozbe/watermelondb\") before versions 0.15.1 and 0.16.2, a maliciously crafted record ID can exploit a SQL Injection vulnerability in iOS adapter implementation and cause the app to delete all or selected records from the database, generally causing the app to become unusable. This may happen in apps that don\u0027t validate IDs (valid IDs are `/^[a-zA-Z0-9_-.]+$/`) and use Watermelon Sync or low-level `database.adapter.destroyDeletedRecords` method. The integrity risk is low due to the fact that maliciously deleted records won\u0027t synchronize, so logout-login will restore all data, although some local changes may be lost if the malicious deletion causes the sync process to fail to proceed to push stage. No way to breach confidentiality with this vulnerability is known. Full exploitation of SQL Injection is mitigated, because it\u0027s not possible to nest an insert/update query inside a delete query in SQLite, and it\u0027s not possible to pass a semicolon-separated second query. There\u0027s also no known practicable way to breach confidentiality by selectively deleting records, because those records will not be synchronized. It\u0027s theoretically possible that selective record deletion could cause an app to behave insecurely if lack of a record is used to make security decisions by the app. This is patched in versions 0.15.1, 0.16.2, and 0.16.1-fix"
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-89",
"description": "CWE-89: Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2020-06-03T16:50:12",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025"
}
],
"source": {
"advisory": "GHSA-38f9-m297-6q9g",
"discovery": "UNKNOWN"
},
"title": "DoS or local data modification via malicious record IDs in WatermelonDB",
"x_legacyV4Record": {
"CVE_data_meta": {
"ASSIGNER": "security-advisories@github.com",
"ID": "CVE-2020-4035",
"STATE": "PUBLIC",
"TITLE": "DoS or local data modification via malicious record IDs in WatermelonDB"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "WatermelonDB",
"version": {
"version_data": [
{
"version_value": "\u003c 0.15.1"
},
{
"version_value": "\u003e= 0.16.0, \u003c 0.16.2"
}
]
}
}
]
},
"vendor_name": "Nozbe"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "In WatermelonDB (NPM package \"@nozbe/watermelondb\") before versions 0.15.1 and 0.16.2, a maliciously crafted record ID can exploit a SQL Injection vulnerability in iOS adapter implementation and cause the app to delete all or selected records from the database, generally causing the app to become unusable. This may happen in apps that don\u0027t validate IDs (valid IDs are `/^[a-zA-Z0-9_-.]+$/`) and use Watermelon Sync or low-level `database.adapter.destroyDeletedRecords` method. The integrity risk is low due to the fact that maliciously deleted records won\u0027t synchronize, so logout-login will restore all data, although some local changes may be lost if the malicious deletion causes the sync process to fail to proceed to push stage. No way to breach confidentiality with this vulnerability is known. Full exploitation of SQL Injection is mitigated, because it\u0027s not possible to nest an insert/update query inside a delete query in SQLite, and it\u0027s not possible to pass a semicolon-separated second query. There\u0027s also no known practicable way to breach confidentiality by selectively deleting records, because those records will not be synchronized. It\u0027s theoretically possible that selective record deletion could cause an app to behave insecurely if lack of a record is used to make security decisions by the app. This is patched in versions 0.15.1, 0.16.2, and 0.16.1-fix"
}
]
},
"impact": {
"cvss": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H",
"version": "3.1"
}
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-89: Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g",
"refsource": "CONFIRM",
"url": "https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g"
},
{
"name": "https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025",
"refsource": "MISC",
"url": "https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025"
}
]
},
"source": {
"advisory": "GHSA-38f9-m297-6q9g",
"discovery": "UNKNOWN"
}
}
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2020-4035",
"datePublished": "2020-06-03T16:50:12",
"dateReserved": "2019-12-30T00:00:00",
"dateUpdated": "2024-08-04T07:52:20.760Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"fkie_nvd": {
"configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:nozbe:watermelondb:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"0.15.1\", \"matchCriteriaId\": \"246C2261-8971-4C09-90AC-15AD5A864A1F\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:nozbe:watermelondb:0.16.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"E9E2E1B2-B5DA-4010-8635-B555309F84C1\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:nozbe:watermelondb:0.16.1:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"2FF01DBC-C248-40CA-BD58-B75E94D99D3D\"}]}]}]",
"descriptions": "[{\"lang\": \"en\", \"value\": \"In WatermelonDB (NPM package \\\"@nozbe/watermelondb\\\") before versions 0.15.1 and 0.16.2, a maliciously crafted record ID can exploit a SQL Injection vulnerability in iOS adapter implementation and cause the app to delete all or selected records from the database, generally causing the app to become unusable. This may happen in apps that don\u0027t validate IDs (valid IDs are `/^[a-zA-Z0-9_-.]+$/`) and use Watermelon Sync or low-level `database.adapter.destroyDeletedRecords` method. The integrity risk is low due to the fact that maliciously deleted records won\u0027t synchronize, so logout-login will restore all data, although some local changes may be lost if the malicious deletion causes the sync process to fail to proceed to push stage. No way to breach confidentiality with this vulnerability is known. Full exploitation of SQL Injection is mitigated, because it\u0027s not possible to nest an insert/update query inside a delete query in SQLite, and it\u0027s not possible to pass a semicolon-separated second query. There\u0027s also no known practicable way to breach confidentiality by selectively deleting records, because those records will not be synchronized. It\u0027s theoretically possible that selective record deletion could cause an app to behave insecurely if lack of a record is used to make security decisions by the app. This is patched in versions 0.15.1, 0.16.2, and 0.16.1-fix\"}, {\"lang\": \"es\", \"value\": \"En WatermelonDB (paquete NPM \\\"@nozbe/watermelondb\\\") versiones anteriores a 0.15.1 y 0.16.2, un ID de registro dise\\u00f1ado con fines maliciosos puede explotar una vulnerabilidad de inyecci\\u00f3n SQL en la implementaci\\u00f3n del adaptador iOS y causar que la aplicaci\\u00f3n elimine todo o registros seleccionados de la base de datos, por lo general, la aplicaci\\u00f3n queda inutilizable. Esto puede suceder en aplicaciones que no comprueban los ID (los ID v\\u00e1lidos son \\\"/^[a-zA-Z0-9_-.]+$/\\\") y usan Watermelon Sync o el m\\u00e9todo \\\"database.adapter.destroyDeletedRecords\\\" de bajo nivel . El riesgo de integridad es bajo debido al hecho de que los registros eliminados maliciosamente no se sincronizar\\u00e1n, por lo que el inicio de sesi\\u00f3n cerrar\\u00e1 todos los datos, aunque algunos cambios locales pueden perderse si la eliminaci\\u00f3n maliciosa causa que el proceso de sincronizaci\\u00f3n no avance a la etapa de inserci\\u00f3n. No se conoce ninguna manera de violar la confidencialidad con esta vulnerabilidad. Una explotaci\\u00f3n completa de la inyecci\\u00f3n SQL se mitiga, porque no es posible anidar una consulta de inserci\\u00f3n/actualizaci\\u00f3n dentro de una consulta de eliminaci\\u00f3n en SQLite, y no es posible pasar una segunda consulta separada por punto y coma. Tampoco se conoce una manera pr\\u00e1ctica de violar la confidencialidad mediante la eliminaci\\u00f3n selectiva de registros, porque esos registros no se sincronizar\\u00e1n. Te\\u00f3ricamente es posible que la eliminaci\\u00f3n de registros selectiva pueda hacer que una aplicaci\\u00f3n se comporte de forma no segura si la falta de un registro para tomar decisiones de seguridad es usada por la aplicaci\\u00f3n. Esto est\\u00e1 parcheado en las versiones 0.15.1, 0.16.2 y 0.16.1-fix\"}]",
"id": "CVE-2020-4035",
"lastModified": "2024-11-21T05:32:11.750",
"metrics": "{\"cvssMetricV31\": [{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H\", \"baseScore\": 5.9, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"LOW\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 1.6, \"impactScore\": 4.2}, {\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H\", \"baseScore\": 5.9, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"LOW\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 1.6, \"impactScore\": 4.2}], \"cvssMetricV2\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"2.0\", \"vectorString\": \"AV:N/AC:L/Au:S/C:N/I:P/A:P\", \"baseScore\": 5.5, \"accessVector\": \"NETWORK\", \"accessComplexity\": \"LOW\", \"authentication\": \"SINGLE\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"PARTIAL\", \"availabilityImpact\": \"PARTIAL\"}, \"baseSeverity\": \"MEDIUM\", \"exploitabilityScore\": 8.0, \"impactScore\": 4.9, \"acInsufInfo\": false, \"obtainAllPrivilege\": false, \"obtainUserPrivilege\": false, \"obtainOtherPrivilege\": false, \"userInteractionRequired\": false}]}",
"published": "2020-06-03T17:15:26.153",
"references": "[{\"url\": \"https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025\", \"source\": \"security-advisories@github.com\", \"tags\": [\"Patch\", \"Third Party Advisory\"]}, {\"url\": \"https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g\", \"source\": \"security-advisories@github.com\", \"tags\": [\"Third Party Advisory\"]}, {\"url\": \"https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Patch\", \"Third Party Advisory\"]}, {\"url\": \"https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Third Party Advisory\"]}]",
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Modified",
"weaknesses": "[{\"source\": \"security-advisories@github.com\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-89\"}]}]"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2020-4035\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2020-06-03T17:15:26.153\",\"lastModified\":\"2024-11-21T05:32:11.750\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In WatermelonDB (NPM package \\\"@nozbe/watermelondb\\\") before versions 0.15.1 and 0.16.2, a maliciously crafted record ID can exploit a SQL Injection vulnerability in iOS adapter implementation and cause the app to delete all or selected records from the database, generally causing the app to become unusable. This may happen in apps that don\u0027t validate IDs (valid IDs are `/^[a-zA-Z0-9_-.]+$/`) and use Watermelon Sync or low-level `database.adapter.destroyDeletedRecords` method. The integrity risk is low due to the fact that maliciously deleted records won\u0027t synchronize, so logout-login will restore all data, although some local changes may be lost if the malicious deletion causes the sync process to fail to proceed to push stage. No way to breach confidentiality with this vulnerability is known. Full exploitation of SQL Injection is mitigated, because it\u0027s not possible to nest an insert/update query inside a delete query in SQLite, and it\u0027s not possible to pass a semicolon-separated second query. There\u0027s also no known practicable way to breach confidentiality by selectively deleting records, because those records will not be synchronized. It\u0027s theoretically possible that selective record deletion could cause an app to behave insecurely if lack of a record is used to make security decisions by the app. This is patched in versions 0.15.1, 0.16.2, and 0.16.1-fix\"},{\"lang\":\"es\",\"value\":\"En WatermelonDB (paquete NPM \\\"@nozbe/watermelondb\\\") versiones anteriores a 0.15.1 y 0.16.2, un ID de registro dise\u00f1ado con fines maliciosos puede explotar una vulnerabilidad de inyecci\u00f3n SQL en la implementaci\u00f3n del adaptador iOS y causar que la aplicaci\u00f3n elimine todo o registros seleccionados de la base de datos, por lo general, la aplicaci\u00f3n queda inutilizable. Esto puede suceder en aplicaciones que no comprueban los ID (los ID v\u00e1lidos son \\\"/^[a-zA-Z0-9_-.]+$/\\\") y usan Watermelon Sync o el m\u00e9todo \\\"database.adapter.destroyDeletedRecords\\\" de bajo nivel . El riesgo de integridad es bajo debido al hecho de que los registros eliminados maliciosamente no se sincronizar\u00e1n, por lo que el inicio de sesi\u00f3n cerrar\u00e1 todos los datos, aunque algunos cambios locales pueden perderse si la eliminaci\u00f3n maliciosa causa que el proceso de sincronizaci\u00f3n no avance a la etapa de inserci\u00f3n. No se conoce ninguna manera de violar la confidencialidad con esta vulnerabilidad. Una explotaci\u00f3n completa de la inyecci\u00f3n SQL se mitiga, porque no es posible anidar una consulta de inserci\u00f3n/actualizaci\u00f3n dentro de una consulta de eliminaci\u00f3n en SQLite, y no es posible pasar una segunda consulta separada por punto y coma. Tampoco se conoce una manera pr\u00e1ctica de violar la confidencialidad mediante la eliminaci\u00f3n selectiva de registros, porque esos registros no se sincronizar\u00e1n. Te\u00f3ricamente es posible que la eliminaci\u00f3n de registros selectiva pueda hacer que una aplicaci\u00f3n se comporte de forma no segura si la falta de un registro para tomar decisiones de seguridad es usada por la aplicaci\u00f3n. Esto est\u00e1 parcheado en las versiones 0.15.1, 0.16.2 y 0.16.1-fix\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H\",\"baseScore\":5.9,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.6,\"impactScore\":4.2},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H\",\"baseScore\":5.9,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.6,\"impactScore\":4.2}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:L/Au:S/C:N/I:P/A:P\",\"baseScore\":5.5,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"LOW\",\"authentication\":\"SINGLE\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"PARTIAL\",\"availabilityImpact\":\"PARTIAL\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":8.0,\"impactScore\":4.9,\"acInsufInfo\":false,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-89\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:nozbe:watermelondb:*:*:*:*:*:*:*:*\",\"versionEndExcluding\":\"0.15.1\",\"matchCriteriaId\":\"246C2261-8971-4C09-90AC-15AD5A864A1F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:nozbe:watermelondb:0.16.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"E9E2E1B2-B5DA-4010-8635-B555309F84C1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:nozbe:watermelondb:0.16.1:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"2FF01DBC-C248-40CA-BD58-B75E94D99D3D\"}]}]}],\"references\":[{\"url\":\"https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://github.com/Nozbe/WatermelonDB/commit/924c7ae2a8d7d6459656751e5b9b1bf91a218025\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/Nozbe/WatermelonDB/security/advisories/GHSA-38f9-m297-6q9g\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Third Party Advisory\"]}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…