{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-13266 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-13266 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-13266 is a high-severity vulnerability in n/a, published on 27 Aug 2019. 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-2019-13266 and fix it if it is affected.\n\nWhat it is: CVE-2019-13266 is a high-severity vulnerability in n/a, published on 27 Aug 2019. 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-2019-13266 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-2019-13266/ (Markdown: https://insights.sbomify.com/CVE-2019-13266/index.md)","id":"CVE-2019-13266","markdown":"https://insights.sbomify.com/CVE-2019-13266/index.md","name":"CVE-2019-13266","record":{"aliases":["GHSA-49mw-9246-92jq"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link wireless router","requires_auth":"none","summary":"Attackers can leak data from the host network to the guest network by exploiting insufficient compartmentalization in DHCP transaction ID handling.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"archer_c2_v1_firmware","vendor":"tp-link"},{"product":"archer_c3200_v1_firmware","vendor":"tp-link"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-669","name":"Incorrect Resource Transfer Between Spheres"}],"description":"TP-Link Archer C3200 V1 and Archer C2 V1 devices have Insufficient Compartmentalization between a host network and a guest network that are established by the same device. A DHCP Request is sent to the router with a certain Transaction ID field. Following the DHCP protocol, the router responds with an ACK or NAK message. Studying the NAK case revealed that the router erroneously sends the NAK to both Host and Guest networks with the same Transaction ID as found in the DHCP Request. This allows encoding of data to be sent cross-router into the 32-bit Transaction ID field.","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":"Information disclosure in n/a","id":"CVE-2019-13266","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-13267"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-13265"},"products":["n/a"],"published":"2019-08-27","related":[{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2019-13267","kev_date_added":null,"published":"2019-08-27"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2019-13268","kev_date_added":null,"published":"2019-08-27"}],"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-04","vendors":["n/a"]},"summary":"Attackers can leak data from the host network to the guest network by exploiting insufficient compartmentalization in DHCP transaction ID handling.","url":"https://insights.sbomify.com/CVE-2019-13266/"}