{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36127 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36127 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36127 is a medium-severity vulnerability in n/a, published on 7 May 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-36127 and fix it if it is affected.\n\nWhat it is: CVE-2020-36127 is a medium-severity vulnerability in n/a, published on 7 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-36127 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-36127/ (Markdown: https://insights.sbomify.com/CVE-2020-36127/index.md)","id":"CVE-2020-36127","markdown":"https://insights.sbomify.com/CVE-2020-36127/index.md","name":"CVE-2020-36127","record":{"aliases":["GHSA-grp5-5x2w-cr8h"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Pax Technology PAXSTORE","requires_auth":"low_privilege","summary":"Non-administrator users can access base64 encoded p12 certificates and passwords via the PUK signature functionality, exposing sensitive credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"paxstore","vendor":"paxtechnology"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Pax Technology PAXSTORE v7.0.8_20200511171508 and lower is affected by an information disclosure vulnerability. Through the PUK signature functionality, an administrator will not have access to the current p12 certificate and password. When accessing this functionality, the administrator has the option to replace the current certificate and it is not possible to view the certificate password (p12) already deployed on the platform. The replacement p12 certificate returns to users in base64 with its password, which can be accessed by non-administrator users.","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-2020-36127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2020-36128"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-36126"},"products":["n/a"],"published":"2021-05-07","related":[{"cvss_score":8.2,"headline":"Auth bypass in n/a","id":"CVE-2020-36128","kev_date_added":null,"published":"2021-05-07"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2020-36126","kev_date_added":null,"published":"2021-05-07"},{"cvss_score":7.1,"headline":"Missing authorization in n/a","id":"CVE-2020-36125","kev_date_added":null,"published":"2021-05-07"},{"cvss_score":6.5,"headline":"XML external entity in n/a","id":"CVE-2020-36124","kev_date_added":null,"published":"2021-05-07"}],"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":"Non-administrator users can access base64 encoded p12 certificates and passwords via the PUK signature functionality, exposing sensitive credentials.","url":"https://insights.sbomify.com/CVE-2020-36127/"}