# CVE-2019-10805: Exposure of Resource to Wrong Sphere in valib

> Attackers can bypass validation checks in the valib library by tampering with internal properties of crafted JavaScript objects.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pmpr-vc5q-h3jw, SNYK-JS-VALIB-559015

## What is CVE-2019-10805?

CVE-2019-10805 is a high-severity vulnerability in valib, published on 28 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

valib through 2.0.0 allows Internal Property Tampering. A maliciously crafted JavaScript object can bypass several inspection functions provided by valib. Valib uses a built-in function (hasOwnProperty) from the unsafe user-input to examine an object. It is possible for a crafted payload to overwrite this function to manipulate the inspection results to bypass security checks.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2019-10805?

2 open source packages ship an affected version, including valib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `valib` | npm | All versions to 2.0.0 | None |
| `valib` | npm | All versions to 2.0.0 | None |

Products: Sideralis Valib.js.

## How do I fix CVE-2019-10805?

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

## Is CVE-2019-10805 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10805 and fix it if it is affected.

What it is: CVE-2019-10805 is a high-severity vulnerability in valib, published on 28 Feb 2020. 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-2019-10805 in the wild and no public exploit code.

Affected packages and fixed versions:
- valib (npm): affected all versions up to 2.0.0; no fix listed
- valib (npm): affected all versions up to 2.0.0; no fix listed

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

## Sources

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

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