{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-51743 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-51743 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-51743 is a high-severity vulnerability in MarkUsProject Markus, published on 18 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-51743 and fix it if it is affected.\n\nWhat it is: CVE-2024-51743 is a high-severity vulnerability in MarkUsProject Markus, published on 18 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-51743 in the wild and no public exploit code.\n\nAffected product: MarkUsProject Markus. 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-2024-51743/ (Markdown: https://insights.sbomify.com/CVE-2024-51743/index.md)","id":"CVE-2024-51743","markdown":"https://insights.sbomify.com/CVE-2024-51743/index.md","name":"CVE-2024-51743","record":{"aliases":["GHSA-hwgg-qvjx-572x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Markus grading system","requires_auth":"low_privilege","summary":"Authenticated instructors can write arbitrary files to the server, potentially leading to remote code execution in the MarkUs grading application.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"markus","vendor":"markusproject"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"MarkUs is a web application for the submission and grading of student assignments. In versions prior to 2.4.8, an arbitrary file write vulnerability in the update/upload/create file methods in Controllers allows authenticated instructors to write arbitrary files to any location on the web server MarkUs is running on (depending on the permissions of the underlying filesystem). e.g. This can lead to a delayed remote code execution in case an attacker is able to write a Ruby file into the config/initializers/ subfolder of the Ruby on Rails application. MarkUs v2.4.8 has addressed this issue. No known workarounds are available at the application level aside from upgrading.","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":"Arbitrary File Write leading up to remote code execution (instructor accounts)","id":"CVE-2024-51743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt","id":"CVE-2024-51744"},"packages":[],"prev":{"headline":"Redis allows denial-of-service due to malformed ACL selectors","id":"CVE-2024-51741"},"products":["Markus"],"published":"2024-11-18","related":[{"cvss_score":9.1,"headline":"Zip Slip in MarkUs config upload allowing RCE","id":"CVE-2026-25057","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":8,"headline":"MarkUs: Stored XSS in Submission HTML Preview Enables Instructor-Context Actions","id":"CVE-2026-28405","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":7.1,"headline":"MarkUs Arbitrary File Write leading up to remote code execution (student accounts)","id":"CVE-2024-51499","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":6.5,"headline":"MarkUs: Zip bomb in config upload enables DoS","id":"CVE-2026-25962","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":6.5,"headline":"MarkUs has a submission-view IDOR exposes all student submissions","id":"CVE-2026-24900","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":5.7,"headline":"MarkUs vulnerable to Path Traversal","id":"CVE-2024-47820","kev_date_added":null,"published":"2024-11-18"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-19","vendors":["MarkUsProject"]},"summary":"Authenticated instructors can write arbitrary files to the server, potentially leading to remote code execution in the MarkUs grading application.","url":"https://insights.sbomify.com/CVE-2024-51743/"}