{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-12831 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-12831 is a medium-severity vulnerability in n/a, published on 13 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-12831 and fix it if it is affected.\n\nWhat it is: CVE-2020-12831 is a medium-severity vulnerability in n/a, published on 13 May 2020. 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-2020-12831 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-12831/ (Markdown: https://insights.sbomify.com/CVE-2020-12831/index.md)","id":"CVE-2020-12831","markdown":"https://insights.sbomify.com/CVE-2020-12831/index.md","name":"CVE-2020-12831","record":{"aliases":["ALSA-2020:4619","DEBIAN-CVE-2020-12831","GHSA-x83m-q23q-xv5j","RHSA-2020:4619","openSUSE-SU-2024:10583-1"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"FRRouting network software","requires_auth":"none","summary":"An attacker can read sensitive configuration data because the init script creates world-readable files when the split-config feature is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"free_range_routing","vendor":"linuxfoundation"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readable default permissions, leading to a possible information leak via tools/frr.in and tools/frrcommon.sh.in. NOTE: some parties consider this user error, not a vulnerability, because the permissions are under the control of the user before any sensitive information is present in the file","ecosystems":["AlmaLinux:8","Red Hat:enterprise_linux:8::appstream","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2020-12831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":6,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2020-12832"},"packages":[{"ecosystem":"AlmaLinux:8","fixed":["7.0-10.el8"],"introduced":["0"],"last_affected":[],"package":"frr-contrib","purl":"pkg:rpm/almalinux/frr-contrib","source":"ALSA-2020:4619"},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","fixed":["0:7.0-10.el8"],"introduced":["0"],"last_affected":[],"package":"frr","purl":"pkg:rpm/redhat/frr","source":"RHSA-2020:4619"},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","fixed":["0:7.0-10.el8"],"introduced":["0"],"last_affected":[],"package":"frr-contrib","purl":"pkg:rpm/redhat/frr-contrib","source":"RHSA-2020:4619"},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","fixed":["0:7.0-10.el8"],"introduced":["0"],"last_affected":[],"package":"frr-debuginfo","purl":"pkg:rpm/redhat/frr-debuginfo","source":"RHSA-2020:4619"},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","fixed":["0:7.0-10.el8"],"introduced":["0"],"last_affected":[],"package":"frr-debugsource","purl":"pkg:rpm/redhat/frr-debugsource","source":"RHSA-2020:4619"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["7.5.1-3.1"],"introduced":["0"],"last_affected":[],"package":"frr","purl":"pkg:rpm/opensuse/frr\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:10583-1"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-12830"},"products":["n/a"],"published":"2020-05-13","related":[],"sources":[{"class":"attribution","licence":"MIT","name":"AlmaLinux","prefix":"ALSA"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can read sensitive configuration data because the init script creates world-readable files when the split-config feature is enabled.","url":"https://insights.sbomify.com/CVE-2020-12831/"}