{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12847 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12847 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12847 is a high-severity vulnerability in n/a, published on 3 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-12847 and fix it if it is affected.\n\nWhat it is: CVE-2019-12847 is a high-severity vulnerability in n/a, published on 3 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-12847 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-12847/ (Markdown: https://insights.sbomify.com/CVE-2019-12847/index.md)","id":"CVE-2019-12847","markdown":"https://insights.sbomify.com/CVE-2019-12847/index.md","name":"CVE-2019-12847","record":{"aliases":["GHSA-3h7w-w4qf-f3pr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JetBrains Hub","requires_auth":"high_privilege","summary":"Administrators can view cleartext SMTP passwords in audit logs if passwords were unchanged since 2017 and old logs remain.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hub","vendor":"jetbrains"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"In JetBrains Hub versions earlier than 2018.4.11298, the audit events for SMTPSettings show a cleartext password to the admin user. It is only relevant in cases where a password has not changed since 2017, and if the audit log still contains events from before that period.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2019-12847","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-12850"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-12846"},"products":["n/a"],"published":"2019-07-03","related":[{"cvss_score":10,"headline":"Auth bypass in Hub","id":"CVE-2026-50242","kev_date_added":null,"published":"2026-06-19"},{"cvss_score":9.8,"headline":"Weak cryptography in Hub","id":"CVE-2026-56141","kev_date_added":null,"published":"2026-06-19"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-25262","kev_date_added":null,"published":"2022-02-25"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2021-43183","kev_date_added":null,"published":"2021-11-09"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-36209","kev_date_added":null,"published":"2021-08-06"},{"cvss_score":9.6,"headline":"Privilege escalation in Hub","id":"CVE-2026-56142","kev_date_added":null,"published":"2026-06-19"},{"cvss_score":9.1,"headline":"Auth bypass in Hub","id":"CVE-2026-25848","kev_date_added":null,"published":"2026-02-09"}],"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":"Administrators can view cleartext SMTP passwords in audit logs if passwords were unchanged since 2017 and old logs remain.","url":"https://insights.sbomify.com/CVE-2019-12847/"}