{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-44796 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-44796 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-44796 is a critical vulnerability in n/a, published on 7 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-44796 and fix it if it is affected.\n\nWhat it is: CVE-2022-44796 is a critical vulnerability in n/a, published on 7 Nov 2022. 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-2022-44796 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-2022-44796/ (Markdown: https://insights.sbomify.com/CVE-2022-44796/index.md)","id":"CVE-2022-44796","markdown":"https://insights.sbomify.com/CVE-2022-44796/index.md","name":"CVE-2022-44796","record":{"aliases":["GHSA-39pq-3mh9-m5qg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Backup appliance software","requires_auth":"none","summary":"Weak JWT secret generation allows attackers to forge tokens and gain unauthorized access to the Web UI.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ootbi","vendor":"objectfirst"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"An issue was discovered in Object First Ootbi BETA build 1.0.7.712. The authorization service has a flow that allows getting access to the Web UI without knowing credentials. For signing, the JWT token uses a secret key that is generated through a function that doesn't produce cryptographically strong sequences. An attacker can predict these sequences and generate a JWT token. As a result, an attacker can get access to the Web UI. This is fixed in Object First Ootbi BETA build 1.0.13.1611.","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-2022-44796","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"btcd mishandles witness size checking","id":"CVE-2022-44797"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2022-44795"},"products":["n/a"],"published":"2022-11-07","related":[{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2022-44794","kev_date_added":null,"published":"2022-11-07"},{"cvss_score":6.5,"headline":"Weak cryptography in n/a","id":"CVE-2022-44795","kev_date_added":null,"published":"2022-11-07"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-01","vendors":["n/a"]},"summary":"Weak JWT secret generation allows attackers to forge tokens and gain unauthorized access to the Web UI.","url":"https://insights.sbomify.com/CVE-2022-44796/"}