{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12270 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12270 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12270 is a high-severity vulnerability in n/a, published on 21 May 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-12270 and fix it if it is affected.\n\nWhat it is: CVE-2019-12270 is a high-severity vulnerability in n/a, published on 21 May 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-12270 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-12270/ (Markdown: https://insights.sbomify.com/CVE-2019-12270/index.md)","id":"CVE-2019-12270","markdown":"https://insights.sbomify.com/CVE-2019-12270/index.md","name":"CVE-2019-12270","record":{"aliases":["GHSA-q9g8-f5hf-9356"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Document processing server","requires_auth":"none","summary":"OpenText Brava! Server installs with excessive default permissions on a document cache share, allowing unauthorized users to read or modify processed documents.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"brava\\!","vendor":"opentext"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"OpenText Brava! Enterprise and Brava! Server 7.5 through 16.4 configure excessive permissions by default on Windows. During installation, a displaylistcache file share is created on the Windows server with full read and write permissions for the Everyone group at both the NTFS and Share levels. The share is used to retrieve documents for processing, and to store processed documents for display in the browser. The only required share level access is read/write by the JobProcessor service account. At the local filesystem level, the only additional required permissions would be read/write from the servlet engine, such as Tomcat. (The affected server components are not installed with Content Server by default, and must be installed separately.) NOTE: the vendor's position is that customers are not supposed to use this default setting without consulting the documentation.","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":"Misconfiguration in n/a","id":"CVE-2019-12270","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2019-12271"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2019-12269"},"products":["n/a"],"published":"2019-05-21","related":[{"cvss_score":7.8,"headline":"Memory corruption in Brava! Desktop","id":"CVE-2021-31480","kev_date_added":null,"published":"2021-06-15"}],"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":"OpenText Brava! Server installs with excessive default permissions on a document cache share, allowing unauthorized users to read or modify processed documents.","url":"https://insights.sbomify.com/CVE-2019-12270/"}