# CVE-2019-10768: angular Prototype Pollution vulnerability - **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 - **Fix available:** Yes - **Published:** 19 Nov 2019 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2019-10768, GHSA-89mq-4x47-5v83, RHSA-2022:8849, RHSA-2022:8866, RHSA-2023:0274, ROOT-APP-NPM-CVE-2019-10768, SNYK-JS-ANGULAR-534884, UBUNTU-CVE-2019-10768 ## What is CVE-2019-10768? CVE-2019-10768 is a high-severity vulnerability in AngularJS, published on 19 Nov 2019. ### Official description In AngularJS before 1.7.9 the function `merge()` could be tricked into adding or modifying properties of `Object.prototype` using a `__proto__` payload. Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes) ## Which versions are affected by CVE-2019-10768? 2 open source packages ship an affected version, including angular. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `angular` | npm | All versions | 1.7.9 | | `angular` | npm | All versions | 1.7.9 | | `XStatic-Angular-common` | Red Hat:openstack:16.1::el8 | All versions | 1:1.5.8.0-13.el8ost | | `python-XStatic-Angular` | Red Hat:openstack:16.1::el8 | All versions | 1:1.5.8.0-13.el8ost | | `python3-XStatic-Angular` | Red Hat:openstack:16.1::el8 | All versions | 1:1.5.8.0-13.el8ost | | `XStatic-Angular-common` | Red Hat:openstack:16.2::el8 | All versions | 1:1.5.8.0-13.el8ost | | `python-XStatic-Angular` | Red Hat:openstack:16.2::el8 | All versions | 1:1.5.8.0-13.el8ost | | `python3-XStatic-Angular` | Red Hat:openstack:16.2::el8 | All versions | 1:1.5.8.0-13.el8ost | | `XStatic-Angular-common` | Red Hat:openstack:17.0::el9 | All versions | 1:1.5.8.0-15.el9ost | | `python-XStatic-Angular` | Red Hat:openstack:17.0::el9 | All versions | 1:1.5.8.0-15.el9ost | | `python3-XStatic-Angular` | Red Hat:openstack:17.0::el9 | All versions | 1:1.5.8.0-15.el9ost | Products: Angularjs Angularjs. ## How do I fix CVE-2019-10768? Upgrade angular to 1.7.9 or later. ## Is CVE-2019-10768 being exploited? There is no known exploitation of CVE-2019-10768 in the wild and no public exploit code. ## Other vulnerabilities in AngularJS - [CVE-2019-14863](https://insights.sbomify.com/CVE-2019-14863/): AngularJS Cross-site Scripting due to failure to sanitize `xlink.href` attributes (high 7.1) - [CVE-2020-7676](https://insights.sbomify.com/CVE-2020-7676/): Angular vulnerable to Cross-site Scripting (medium 5.4) - [CVE-2023-26116](https://insights.sbomify.com/CVE-2023-26116/): angular vulnerable to regular expression denial of service via the angular.copy() utility (medium 5.3) - [CVE-2023-26117](https://insights.sbomify.com/CVE-2023-26117/): angular vulnerable to regular expression denial of service via the $resource service (medium 5.3) - [CVE-2023-26118](https://insights.sbomify.com/CVE-2023-26118/): angular vulnerable to regular expression denial of service via the element (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-10768 and fix it if it is affected. What it is: CVE-2019-10768 is a high-severity vulnerability in AngularJS, published on 19 Nov 2019. Exploitation: There is no known exploitation of CVE-2019-10768 in the wild and no public exploit code. Affected packages and fixed versions: - angular (npm): affected all versions; fixed in 1.7.9 - angular (npm): affected all versions; fixed in 1.7.9 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-10768/ (Markdown: https://insights.sbomify.com/CVE-2019-10768/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10768 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10768 - OSV: https://osv.dev/vulnerability/CVE-2019-10768 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-10768/ Summaries are generated and may contain mistakes; the official description above is the record.