# CVE-2020-1674: DO NOT USE THIS CANDIDATE NUMBER.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 Oct 2020
- **Updated:** 5 Jan 2021
- **Also known as:** GHSA-3674-2vm4-7jg2

## What is CVE-2020-1674?

CVE-2020-1674 is a vulnerability, published on 16 Oct 2020. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a vulnerability. Notes: The fix resolved an issue when MACsec replay-protect was enabled and the replay-protect-window value was set to zero, Junos OS was incorrectly configuring the value to MAX_WINDOW size. Hence this is not a vulnerability and this CVE ID assignment has been withdrawn

## Which versions are affected by CVE-2020-1674?


## How do I fix CVE-2020-1674?

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

## Is CVE-2020-1674 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1674 and fix it if it is affected.

What it is: CVE-2020-1674 is a vulnerability, published on 16 Oct 2020. 
Exploitation: There is no known exploitation of CVE-2020-1674 in the wild and no public exploit code.

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-2020-1674/ (Markdown: https://insights.sbomify.com/CVE-2020-1674/index.md)
```

## Sources

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

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