{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40278 exists.","fix":"No fix has been published for CVE-2023-40278 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-40278 is a high-severity vulnerability in n/a, published on 19 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-40278 and fix it if it is affected.\n\nWhat it is: CVE-2023-40278 is a high-severity vulnerability in n/a, published on 19 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40278 exists.\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-2023-40278/ (Markdown: https://insights.sbomify.com/CVE-2023-40278/index.md)","id":"CVE-2023-40278","markdown":"https://insights.sbomify.com/CVE-2023-40278/index.md","name":"CVE-2023-40278","record":{"aliases":["GHSA-r6v7-852g-qprq"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenClinic GA","requires_auth":"none","summary":"An attacker can determine if specific appointments exist in OpenClinic GA by manipulating the AppointmentUid parameter, leading to information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"openclinic_ga","vendor":"openclinic_ga_project"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in OpenClinic GA 5.247.01. An Information Disclosure vulnerability has been identified in the printAppointmentPdf.jsp component of OpenClinic GA. By changing the AppointmentUid parameter, an attacker can determine whether a specific appointment exists based on the error message.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2024-04-15","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-04-15","kind":"exploitdb","ref":"51994","stars":null,"title":"OpenClinic GA 5.247.01 - Information Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2023-40278","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2023-40279"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-40277"},"products":["n/a"],"published":"2024-03-19","related":[{"cvss_score":10,"headline":"Command injection in OpenClinic","id":"CVE-2020-27227","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":9.8,"headline":"Security feature bypass in OpenClinic GA","id":"CVE-2020-14484","kev_date_added":null,"published":"2020-07-20"},{"cvss_score":9.8,"headline":"Auth bypass in OpenClinic GA","id":"CVE-2020-14485","kev_date_added":null,"published":"2020-07-20"},{"cvss_score":9.8,"headline":"Auth bypass in OpenClinic GA","id":"CVE-2020-14494","kev_date_added":null,"published":"2020-07-20"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2023-40275","kev_date_added":null,"published":"2024-03-19"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2023-40276","kev_date_added":null,"published":"2024-03-19"},{"cvss_score":8.8,"headline":"Privilege escalation in OpenClinic","id":"CVE-2020-27228","kev_date_added":null,"published":"2021-04-13"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-10","vendors":["n/a"]},"summary":"An attacker can determine if specific appointments exist in OpenClinic GA by manipulating the AppointmentUid parameter, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2023-40278/"}