{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31149 exists.","fix":"No fix has been published for CVE-2022-31149 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31149 is a high-severity vulnerability in activitywatch, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-31149 and fix it if it is affected.\n\nWhat it is: CVE-2022-31149 is a high-severity vulnerability in activitywatch, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31149 exists.\n\nAffected product: activitywatch. 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-31149/ (Markdown: https://insights.sbomify.com/CVE-2022-31149/index.md)","id":"CVE-2022-31149","markdown":"https://insights.sbomify.com/CVE-2022-31149/index.md","name":"CVE-2022-31149","record":{"aliases":["GHSA-v9fg-6g9j-h4x4"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ActivityWatch time tracker","requires_auth":"none","summary":"Attackers can bypass origin checks via DNS rebinding to access the ActivityWatch REST API, exposing user activity data.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"activitywatch","vendor":"activitywatch"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"ActivityWatch open-source automated time tracker. Versions prior to 0.12.0b2 are vulnerable to DNS rebinding attacks. This vulnerability impacts everyone running ActivityWatch and gives the attacker full access to the ActivityWatch REST API. Users should upgrade to v0.12.0b2 or later to receive a patch. As a workaround, block DNS lookups that resolve to 127.0.0.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"ActivityWatch vulnerable to DNS rebinding attack","id":"CVE-2022-31149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"CRLF injection in request headers","id":"CVE-2022-31150"},"packages":[],"prev":{"headline":"Persistent cross site scripting in customer module in Shopware","id":"CVE-2022-31148"},"products":["activitywatch"],"published":"2022-09-07","related":[{"cvss_score":9.6,"headline":"Activity Watch vulnerable to command execution on macOS via printAppTitle.scpt","id":"CVE-2021-32692","kev_date_added":null,"published":"2022-12-23"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["ActivityWatch"]},"summary":"Attackers can bypass origin checks via DNS rebinding to access the ActivityWatch REST API, exposing user activity data.","url":"https://insights.sbomify.com/CVE-2022-31149/"}