{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32033 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32033 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32033 is a medium-severity vulnerability in n/a, published on 16 Jun 2021. 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-2021-32033 and fix it if it is affected.\n\nWhat it is: CVE-2021-32033 is a medium-severity vulnerability in n/a, published on 16 Jun 2021. 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-2021-32033 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-2021-32033/ (Markdown: https://insights.sbomify.com/CVE-2021-32033/index.md)","id":"CVE-2021-32033","markdown":"https://insights.sbomify.com/CVE-2021-32033/index.md","name":"CVE-2021-32033","record":{"aliases":["GHSA-x83x-q4rh-hv7j"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NFC security token","requires_auth":"none","summary":"Attackers with physical access can manipulate the device clock to predict future TOTP passwords, bypassing two-factor authentication.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"slim_nfc_70_firmware","vendor":"protectimus"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-335","name":"Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)"}],"description":"Protectimus SLIM NFC 70 10.01 devices allow a Time Traveler attack in which attackers can predict TOTP passwords in certain situations. The time value used by the device can be set independently from the used seed value for generating time-based one-time passwords, without authentication. Thus, an attacker with short-time physical access to a device can set the internal real-time clock (RTC) to the future, generate one-time passwords, and reset the clock to the current time. This allows the generation of valid future time-based one-time passwords without having further access to the hardware token.","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":"Weak cryptography in n/a","id":"CVE-2021-32033","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of Service and Data Integrity vulnerability in features command","id":"CVE-2021-32036"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-32032"},"products":["n/a"],"published":"2021-06-16","related":[],"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-03","vendors":["n/a"]},"summary":"Attackers with physical access can manipulate the device clock to predict future TOTP passwords, bypassing two-factor authentication.","url":"https://insights.sbomify.com/CVE-2021-32033/"}