{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36192 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36192 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36192 is a medium-severity missing authorization vulnerability in n/a, published on 18 Jan 2021. 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-36192 and fix it if it is affected.\n\nWhat it is: CVE-2020-36192 is a medium-severity missing authorization vulnerability in n/a, published on 18 Jan 2021. 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-36192 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-36192/ (Markdown: https://insights.sbomify.com/CVE-2020-36192/index.md)","id":"CVE-2020-36192","markdown":"https://insights.sbomify.com/CVE-2020-36192/index.md","name":"CVE-2020-36192","record":{"aliases":["GHSA-38cv-vxxh-c9ff"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MantisBT plugin","requires_auth":"none","summary":"Attackers can view private issue summaries and link unauthorized issues to changesets in the MantisBT Source Integration plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"source_integration","vendor":"mantisbt"}],"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":[],"description":"An issue was discovered in the Source Integration plugin before 2.4.1 for MantisBT. An attacker can gain access to the Summary field of private Issues (either marked as Private, or part of a private Project), if they are attached to an existing Changeset. The information is visible on the view.php page, as well as on the list.php page (a pop-up on the Affected Issues id hyperlink). Additionally, if the attacker has \"Update threshold\" in the plugin's configuration (set to the \"updater\" access level by default), then they can link any Issue to a Changeset by entering the Issue's Id, even if they do not have access to it.","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":"Missing authorization in n/a","id":"CVE-2020-36192","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"PEAR Archive_Tar Improper Link Resolution","id":"CVE-2020-36193"},"packages":[],"prev":{"headline":"Cross-Site Request Forgery in JupyterHub","id":"CVE-2020-36191"},"products":["n/a"],"published":"2021-01-18","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-8981","kev_date_added":null,"published":"2020-02-13"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-16362","kev_date_added":null,"published":"2018-09-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-6958","kev_date_added":null,"published":"2017-03-17"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can view private issue summaries and link unauthorized issues to changesets in the MantisBT Source Integration plugin.","url":"https://insights.sbomify.com/CVE-2020-36192/"}