{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7212 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-7212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-7212 is a high-severity vulnerability in n/a, published on 24 Apr 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-7212 and fix it if it is affected.\n\nWhat it is: CVE-2019-7212 is a high-severity vulnerability in n/a, published on 24 Apr 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-7212 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-7212/ (Markdown: https://insights.sbomify.com/CVE-2019-7212/index.md)","id":"CVE-2019-7212","markdown":"https://insights.sbomify.com/CVE-2019-7212/index.md","name":"CVE-2019-7212","record":{"aliases":["GHSA-vhxc-xrx4-c2rp"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SmarterMail email server","requires_auth":"none","summary":"An unauthenticated attacker can access other users' emails and attachments due to hardcoded secret keys in SmarterMail.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smartermail","vendor":"smartertools"}],"cvss":{"score":8.2,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"SmarterTools SmarterMail 16.x before build 6985 has hardcoded secret keys. An unauthenticated attacker could access other users’ emails and file attachments. It was also possible to interact with mailing lists.","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":"Hardcoded credentials in n/a","id":"CVE-2019-7212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2019-7213"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-7211"},"products":["n/a"],"published":"2019-04-24","related":[{"cvss_score":10,"headline":"SmarterTools SmarterMail Unrestricted Upload of File with Dangerous Type","id":"CVE-2025-52691","kev_date_added":"2026-01-26","published":"2025-12-29"},{"cvss_score":9.3,"headline":"SmarterTools SmarterMail Missing Authentication for Critical Function","id":"CVE-2026-24423","kev_date_added":"2026-02-05","published":"2026-01-23"},{"cvss_score":9.3,"headline":"SmarterTools SmarterMail Authentication Bypass Using an Alternate Path or Channel","id":"CVE-2026-23760","kev_date_added":"2026-01-26","published":"2026-01-22"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-32234","kev_date_added":null,"published":"2021-11-17"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2019-7214","kev_date_added":null,"published":"2019-04-24"},{"cvss_score":8.7,"headline":"SmarterTools SmarterMail \u003c Build 9560 Server Local File Inclusion via the /api/v1/report/summary/{type} API","id":"CVE-2026-7807","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":8.2,"headline":"SmarterTools SmarterMail \u003c Build 9610 Cryptographic Weakness via Weak RNG","id":"CVE-2026-40514","kev_date_added":null,"published":"2026-04-27"}],"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":"An unauthenticated attacker can access other users' emails and attachments due to hardcoded secret keys in SmarterMail.","url":"https://insights.sbomify.com/CVE-2019-7212/"}