{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36248 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36248 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36248 is a low-severity vulnerability in n/a, published on 19 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-36248 and fix it if it is affected.\n\nWhat it is: CVE-2020-36248 is a low-severity vulnerability in n/a, published on 19 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-36248 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-36248/ (Markdown: https://insights.sbomify.com/CVE-2020-36248/index.md)","id":"CVE-2020-36248","markdown":"https://insights.sbomify.com/CVE-2020-36248/index.md","name":"CVE-2020-36248","record":{"aliases":["GHSA-v933-rrv9-44p3"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ownCloud Android app","requires_auth":"low_privilege","summary":"Attackers can bypass the PIN lock in the ownCloud Android app by restoring a crafted backup archive containing a PIN preference value.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"owncloud_client","vendor":"owncloud"}],"cvss":{"score":3.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AC:H/AV:P/A:N/C:H/I:N/PR:L/S:U/UI:R","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"The ownCloud application before 2.15 for Android allows attackers to use adb to include a PIN preferences value in a backup archive, and consequently bypass the PIN lock feature by restoring from this archive.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2020-36248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-36249"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-36247"},"products":["n/a"],"published":"2021-02-19","related":[{"cvss_score":6.8,"headline":"Missing authorization in n/a","id":"CVE-2022-25338","kev_date_added":null,"published":"2022-04-07"},{"cvss_score":6.2,"headline":"ownCloud Android app vulnerable to SQL Injection","id":"CVE-2023-23948","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":6.1,"headline":"Security feature bypass in n/a","id":"CVE-2020-36250","kev_date_added":null,"published":"2021-02-19"},{"cvss_score":5.5,"headline":"Missing authorization in n/a","id":"CVE-2022-25339","kev_date_added":null,"published":"2022-04-07"},{"cvss_score":5,"headline":"ownCloud Android app vulnerable to Path Traversal","id":"CVE-2023-24804","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2015-5955","kev_date_added":null,"published":"2015-10-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass the PIN lock in the ownCloud Android app by restoring a crafted backup archive containing a PIN preference value.","url":"https://insights.sbomify.com/CVE-2020-36248/"}