JVNDB-2021-000112
Vulnerability from jvndb - Published: 2021-12-22 15:07 - Updated:2021-12-22 15:07
Severity ?
Summary
Android Apps developed using Yappli fails to restrict custom URL schemes properly
Details
Yappli provided by Yappli, Inc. is an application development platform.
Android Apps that are developed with Yappli provide the function to access a requested URL using Custom URL Scheme.
The access to the function is not restricted properly (CWE-939) which may be exploited to direct the App to connect to unintended sites.
RyotaK reported and coordinated with the developer to fix this vulnerability.
After coordination was completed, this case was reported to IPA, and JPCERT/CC coordinated with the developer for the publication under Information Security Early Warning Partnership.
References
Impacted products
| Vendor | Product | |
|---|---|---|
{
"@rdf:about": "https://jvndb.jvn.jp/en/contents/2021/JVNDB-2021-000112.html",
"dc:date": "2021-12-22T15:07+09:00",
"dcterms:issued": "2021-12-22T15:07+09:00",
"dcterms:modified": "2021-12-22T15:07+09:00",
"description": "Yappli provided by Yappli, Inc. is an application development platform.\r\nAndroid Apps that are developed with Yappli provide the function to access a requested URL using Custom URL Scheme.\r\nThe access to the function is not restricted properly (CWE-939) which may be exploited to direct the App to connect to unintended sites.\r\n\r\nRyotaK reported and coordinated with the developer to fix this vulnerability.\r\nAfter coordination was completed, this case was reported to IPA, and JPCERT/CC coordinated with the developer for the publication under Information Security Early Warning Partnership.",
"link": "https://jvndb.jvn.jp/en/contents/2021/JVNDB-2021-000112.html",
"sec:cpe": {
"#text": "cpe:/a:yappli:yappli",
"@product": "Yappli",
"@vendor": "Yappli, Inc.",
"@version": "2.2"
},
"sec:cvss": [
{
"@score": "4.3",
"@severity": "Medium",
"@type": "Base",
"@vector": "AV:N/AC:M/Au:N/C:N/I:P/A:N",
"@version": "2.0"
},
{
"@score": "5.5",
"@severity": "Medium",
"@type": "Base",
"@vector": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"@version": "3.0"
}
],
"sec:identifier": "JVNDB-2021-000112",
"sec:references": [
{
"#text": "https://jvn.jp/en/jp/JVN66422035/index.html",
"@id": "JVN#66422035",
"@source": "JVN"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2021-20873",
"@id": "CVE-2021-20873",
"@source": "CVE"
},
{
"#text": "https://nvd.nist.gov/vuln/detail/CVE-2021-20873",
"@id": "CVE-2021-20873",
"@source": "NVD"
},
{
"#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
"@id": "CWE-264",
"@title": "Permissions(CWE-264)"
}
],
"title": "Android Apps developed using Yappli fails to restrict custom URL schemes properly"
}
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…