{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-8919 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-8919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-8919 is a high-severity vulnerability in n/a, published on 18 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-8919 and fix it if it is affected.\n\nWhat it is: CVE-2019-8919 is a high-severity vulnerability in n/a, published on 18 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-8919 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-2019-8919/ (Markdown: https://insights.sbomify.com/CVE-2019-8919/index.md)","id":"CVE-2019-8919","markdown":"https://insights.sbomify.com/CVE-2019-8919/index.md","name":"CVE-2019-8919","record":{"aliases":["GHSA-pwqg-3r7w-w9hw"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Seafile Android Client","requires_auth":"none","summary":"The Seafile Android Client uses a static IV in CBC mode, allowing attackers to perform chosen-plaintext or dictionary attacks to decrypt private data.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seadroid","vendor":"seafile"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"The seadroid (aka Seafile Android Client) application through 2.2.13 for Android always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.","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":"Weak cryptography in n/a","id":"CVE-2019-8919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-8920"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-8917"},"products":["n/a"],"published":"2019-02-18","related":[],"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":"The Seafile Android Client uses a static IV in CBC mode, allowing attackers to perform chosen-plaintext or dictionary attacks to decrypt private data.","url":"https://insights.sbomify.com/CVE-2019-8919/"}