{"answers":{"affected":"3 open source packages ship an affected version, including libosdp.","exploited":"There is no known exploitation of CVE-2024-52288 in the wild and no public exploit code.","fix":"Upgrade libosdp to 3.0.0 or later.","what":"CVE-2024-52288 is a medium-severity vulnerability in goToMain libosdp, published on 11 Nov 2024. 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-2024-52288 and fix it if it is affected.\n\nWhat it is: CVE-2024-52288 is a medium-severity vulnerability in goToMain libosdp, published on 11 Nov 2024. 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-2024-52288 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libosdp (PyPI): affected all versions; fixed in 3.0.0\n- libosdp (PyPI): affected all versions; fixed in 3.0.0\n- libosdp (PyPI): affected all versions; fixed in 3.0.0\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-52288/ (Markdown: https://insights.sbomify.com/CVE-2024-52288/index.md)","id":"CVE-2024-52288","markdown":"https://insights.sbomify.com/CVE-2024-52288/index.md","name":"CVE-2024-52288","record":{"aliases":["GHSA-xhjw-7vh5-qxqm","PYSEC-2026-1535"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OSDP protocol library","requires_auth":"none","summary":"A Man-in-the-Middle attacker can replay OSDP messages by resetting the RMAC state, bypassing security checks in libosdp.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-924","name":"Improper Enforcement of Message Integrity During Transmission in a Communication Channel"}],"description":"libosdp is an implementation of IEC 60839-11-5 OSDP (Open Supervised Device Protocol) and provides a C library with support for C++, Rust and Python3. In affected versions an unexpected `REPLY_CCRYPT` or `REPLY_RMAC_I` may be introduced into an active stream when they should not be. Once RMAC_I message can be sent during a session, attacker with MITM access to the communication may intercept the original RMAC_I reply and save it. While the session continues, the attacker will record all of the replies and save them, till capturing the message to be replied (can be detected by ID, length or time based on inspection of visual activity next to the reader) Once attacker captures a session with the message to be replayed, he stops resetting the connection and waits for signal to perform the replay to of the PD to CP message (ex: by signaling remotely to the MIMT device or setting a specific timing). In order to replay, the attacker will craft a specific RMAC_I message in the proper seq of the execution, which will result in reverting the RMAC to the beginning of the session. At that phase - attacker can replay all the messages from the beginning of the session. This issue has been addressed in commit `298576d9` which is included in release version 3.0.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"RMAC revert to the beginning of the session in libosdp","id":"CVE-2024-52288","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"authentik has an insecure default configuration for OAuth2 Redirect URIs","id":"CVE-2024-52289"},"packages":[{"ecosystem":"PyPI","fixed":["3.0.0"],"introduced":["0"],"last_affected":[],"package":"libosdp","purl":null,"source":"GHSA-xhjw-7vh5-qxqm"},{"ecosystem":"PyPI","fixed":["3.0.0"],"introduced":["0"],"last_affected":[],"package":"libosdp","purl":"pkg:pypi/libosdp","source":"GHSA-xhjw-7vh5-qxqm"},{"ecosystem":"PyPI","fixed":["3.0.0"],"introduced":["0"],"last_affected":[],"package":"libosdp","purl":"pkg:pypi/libosdp","source":"PYSEC-2026-1535"}],"prev":{"headline":"authentik performs insufficient validation of OAuth scopes","id":"CVE-2024-52287"},"products":["libosdp"],"published":"2024-11-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"partial"},"state":"PUBLISHED","updated":"2024-11-12","vendors":["goToMain"]},"summary":"A Man-in-the-Middle attacker can replay OSDP messages by resetting the RMAC state, bypassing security checks in libosdp.","url":"https://insights.sbomify.com/CVE-2024-52288/"}