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


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Jun 2020
- **Updated:** 3 Jun 2020

## What is CVE-2020-1703?

CVE-2020-1703 is a vulnerability, published on 3 Jun 2020. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: Red Hat Product Security does not consider this as a security flaw. Password changes aren't expected to invalidate existing sessions. Though this is how Kerberos behaves: incrementing kvno will not invalidate any existing service tickets. This is not a concern because the lifetime on service tickets should be set appropriately (initially only a global, now also more finely configurable with the kdcpolicy plugin). This belief is reinforced by our use of mod_session: existing sessions there aren't terminated, but instead wait for expiration

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


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

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

## Is CVE-2020-1703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1703 is a vulnerability, published on 3 Jun 2020. 
Exploitation: There is no known exploitation of CVE-2020-1703 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-1703/ (Markdown: https://insights.sbomify.com/CVE-2020-1703/index.md)
```

## Sources

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

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