# CVE-2012-4985: Security feature bypass in n/a

> Remote attackers can bypass network access controls by sending crafted ARP and ICMP packets, enabling ARP poisoning attacks against unrecognized clients.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pfm6-24jh-98j7

## What is CVE-2012-4985?

CVE-2012-4985 is a medium-severity vulnerability in n/a, published on 5 Dec 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Forescout CounterACT NAC device 6.3.4.1 does not block ARP and ICMP traffic from unrecognized clients, which allows remote attackers to conduct ARP poisoning attacks via crafted packets.

Weakness: CWE-264

## Which versions are affected by CVE-2012-4985?

It affects 1 product.


Products: Forescout Counteract.

## How do I fix CVE-2012-4985?

No fix has been published for CVE-2012-4985 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-4985 being exploited?

There is no known exploitation of CVE-2012-4985 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-28098](https://insights.sbomify.com/CVE-2021-28098/): Privilege escalation in n/a (high 7.8)
- [CVE-2012-4982](https://insights.sbomify.com/CVE-2012-4982/): Open redirect in n/a (medium 5.8)
- [CVE-2012-4983](https://insights.sbomify.com/CVE-2012-4983/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-1825](https://insights.sbomify.com/CVE-2012-1825/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4985 and fix it if it is affected.

What it is: CVE-2012-4985 is a medium-severity vulnerability in n/a, published on 5 Dec 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-4985 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-4985/ (Markdown: https://insights.sbomify.com/CVE-2012-4985/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-4985
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-4985
- OSV: https://osv.dev/vulnerability/CVE-2012-4985

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-4985/
Summaries are generated and may contain mistakes; the official description above is the record.