{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5248 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-5248 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-5248 is a high-severity vulnerability in Glpi-Project Glpi, published on 12 May 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5248 and fix it if it is affected.\n\nWhat it is: CVE-2020-5248 is a high-severity vulnerability in Glpi-Project Glpi, published on 12 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5248 in the wild and no public exploit code.\n\nAffected product: Glpi-Project Glpi. 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-5248/ (Markdown: https://insights.sbomify.com/CVE-2020-5248/index.md)","id":"CVE-2020-5248","markdown":"https://insights.sbomify.com/CVE-2020-5248/index.md","name":"CVE-2020-5248","record":{"aliases":["GHSA-j222-j9mf-h6j9","UBUNTU-CVE-2020-5248"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ITSM web application","requires_auth":"high_privilege","summary":"Attackers can decrypt sensitive data in GLPI instances because the application uses a public, hardcoded encryption key by default.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"glpi","vendor":"glpi-project"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"GLPI before before version 9.4.6 has a vulnerability involving a default encryption key. GLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key. It is possible to change the key before installing GLPI. But on existing instances, data must be reencrypted with the new key. Problem is we can not know which columns or rows in the database are using that; espcially from plugins. Changing the key without updating data would lend in bad password sent from glpi; but storing them again from the UI will work.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-10-09","github_poc":2,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-10-09T12:31:19Z","kind":"github_poc","ref":"https://github.com/venomnis/CVE-2020-5248","stars":6,"title":"Proof of Concept (PoC) for CVE-2020-5248."},{"date":"2021-07-29T00:46:26Z","kind":"github_poc","ref":"https://github.com/Mkway/CVE-2020-5248","stars":0,"title":"CVE-2020-5248"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Public GLPIKEY can be used to decrypt any data in GLPI","id":"CVE-2020-5248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"glpi-project:glpi","products":["glpi-project:glpi"],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"HTTP Response Splitting (Early Hints) in Puma","id":"CVE-2020-5249"},"packages":[],"prev":{"headline":"HTTP Response Splitting in Puma","id":"CVE-2020-5247"},"products":["glpi"],"published":"2020-05-12","related":[{"cvss_score":9.8,"headline":"Teclib GLPI Remote Code Execution","id":"CVE-2022-35914","kev_date_added":"2023-03-07","published":"2022-09-19"},{"cvss_score":10,"headline":"GLPI vulnerable to unallowed PHP script execution","id":"CVE-2023-42802","kev_date_added":null,"published":"2023-11-02"},{"cvss_score":10,"headline":"GLPI vulnerable to SQL injection and Stored XSS via inventory agent request","id":"CVE-2023-28849","kev_date_added":null,"published":"2023-04-05"},{"cvss_score":10,"headline":"SQL injection in GLPI","id":"CVE-2022-35947","kev_date_added":null,"published":"2022-09-14"},{"cvss_score":9.8,"headline":"SQL injection with _actor parameter in GLPI","id":"CVE-2022-31056","kev_date_added":null,"published":"2022-06-28"},{"cvss_score":9.8,"headline":"SQL injection on login page in GLPI","id":"CVE-2022-31061","kev_date_added":null,"published":"2022-06-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-44617","kev_date_added":null,"published":"2022-03-28"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["glpi-project"]},"summary":"Attackers can decrypt sensitive data in GLPI instances because the application uses a public, hardcoded encryption key by default.","url":"https://insights.sbomify.com/CVE-2020-5248/"}