{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-29550 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-29550 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-29550 is a high-severity vulnerability in n/a, published on 23 Dec 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-29550 and fix it if it is affected.\n\nWhat it is: CVE-2020-29550 is a high-severity vulnerability in n/a, published on 23 Dec 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-29550 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-29550/ (Markdown: https://insights.sbomify.com/CVE-2020-29550/index.md)","id":"CVE-2020-29550","markdown":"https://insights.sbomify.com/CVE-2020-29550/index.md","name":"CVE-2020-29550","record":{"aliases":["GHSA-8ph5-9xm8-j5vh"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"URVE Build","requires_auth":"none","summary":"An attacker with access to configuration files or database backups can retrieve cleartext credentials for the MS Office 365 integration service.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"urve","vendor":"urve"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"An issue was discovered in URVE Build 24.03.2020. The password of an integration user account (used for the connection of the MS Office 365 Integration Service) is stored in cleartext in configuration files as well as in the database. The following files contain the password in cleartext: Profiles/urve/files/sql_db.backup, Server/data/pg_wal/000000010000000A000000DD, Server/data/base/16384/18617, and Server/data/base/17202/8708746. This causes the password to be displayed as cleartext in the HTML code as roomsreservationimport_password in /urve/roomsreservationimport/roomsreservationimport/update-HTML5.","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":"Hardcoded credentials in n/a","id":"CVE-2020-29550","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-29551"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2020-29548"},"products":["n/a"],"published":"2020-12-23","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-29552","kev_date_added":null,"published":"2020-12-23"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2020-29551","kev_date_added":null,"published":"2020-12-23"}],"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":"An attacker with access to configuration files or database backups can retrieve cleartext credentials for the MS Office 365 integration service.","url":"https://insights.sbomify.com/CVE-2020-29550/"}