# CVE-2013-6020: Information disclosure in n/a

> Remote attackers can enumerate valid user accounts in Tyler Technologies TaxWeb by observing HTTP status code differences during password recovery requests.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5vjj-5wh5-xg8m

## What is CVE-2013-6020?

CVE-2013-6020 is a medium-severity vulnerability in n/a, published on 28 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

passwordRequestPOST.jsp in Tyler Technologies TaxWeb 3.13.3.1 sends different HTTP status codes for invalid password-recovery requests depending on whether the user account exists, which allows remote attackers to enumerate account names via a series of requests to the (1) Assessor, (2) Recorder, or (3) Treasurer application.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-6020?

It affects 1 product.


Products: Tylertech Taxweb.

## How do I fix CVE-2013-6020?

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

## Is CVE-2013-6020 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6018](https://insights.sbomify.com/CVE-2013-6018/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-6285](https://insights.sbomify.com/CVE-2013-6285/): Information disclosure in n/a (medium 5.0)
- [CVE-2013-6019](https://insights.sbomify.com/CVE-2013-6019/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6020 and fix it if it is affected.

What it is: CVE-2013-6020 is a medium-severity vulnerability in n/a, published on 28 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6020 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-2013-6020/ (Markdown: https://insights.sbomify.com/CVE-2013-6020/index.md)
```

## Sources

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

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