{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-32290 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-32290 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-32290 is a medium-severity missing authorization vulnerability in n/a, published on 6 Jul 2022. 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-2022-32290 and fix it if it is affected.\n\nWhat it is: CVE-2022-32290 is a medium-severity missing authorization vulnerability in n/a, published on 6 Jul 2022. 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-2022-32290 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-32290/ (Markdown: https://insights.sbomify.com/CVE-2022-32290/index.md)","id":"CVE-2022-32290","markdown":"https://insights.sbomify.com/CVE-2022-32290/index.md","name":"CVE-2022-32290","record":{"aliases":["GHSA-vjrr-3c22-j86f"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Mender client","requires_auth":"none","summary":"The Mender client exposes an HTTP proxy on all network interfaces, allowing local network attackers to bypass mTLS and send requests to the server.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mender","vendor":"northern.tech"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The client in Northern.tech Mender 3.2.0, 3.2.1, and 3.2.2 has Incorrect Access Control. It listens on a random, unprivileged TCP port and exposes an HTTP proxy to facilitate API calls from additional client components running on the device. However, it listens on all network interfaces instead of only the localhost interface. Therefore, any client on the same network can connect to this TCP port and send HTTP requests. The Mender Client will forward these requests to the Mender Server. Additionally, if mTLS is set up, the Mender Client will connect to the Mender Server using the device's client certificate, making it possible for the attacker to bypass mTLS authentication and send requests to the Mender Server without direct access to the client certificate and related private key. Accessing the HTTP proxy from the local network doesn't represent a direct threat, because it doesn't expose any device or server-specific data. However, it increases the attack surface and can be a potential vector to exploit other vulnerabilities both on the Client and the Server.","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":"Missing authorization in n/a","id":"CVE-2022-32290","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2022-32291"},"packages":[],"prev":{"headline":"Cross-site request forgery in Popup Builder (WordPress plugin)","id":"CVE-2022-32289"},"products":["n/a"],"published":"2022-07-06","related":[{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-29556","kev_date_added":null,"published":"2022-04-28"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-29555","kev_date_added":null,"published":"2022-04-28"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2024-46948","kev_date_added":null,"published":"2024-11-08"}],"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":"The Mender client exposes an HTTP proxy on all network interfaces, allowing local network attackers to bypass mTLS and send requests to the server.","url":"https://insights.sbomify.com/CVE-2022-32290/"}