# GHSA-28hp-fgcr-2r4h: Cross-Site Scripting via JSONP

> Attackers can execute arbitrary scripts in victim browsers by exploiting untrusted JSONP resource URLs in this npm library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jun 2019

## What is GHSA-28hp-fgcr-2r4h?

GHSA-28hp-fgcr-2r4h is a cross-site scripting vulnerability in angular, published on 27 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

JSONP allows untrusted resource URLs, which provides a vector for attack by malicious actors.

## Which versions are affected by GHSA-28hp-fgcr-2r4h?

2 open source packages ship an affected version, including angular.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `angular` | npm | All versions | 1.6.0 |
| `angular` | npm | All versions | 1.6.0 |

## How do I fix GHSA-28hp-fgcr-2r4h?

Upgrade angular to 1.6.0 or later.

## Is GHSA-28hp-fgcr-2r4h being exploited?

There is no known exploitation of GHSA-28hp-fgcr-2r4h in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-28hp-fgcr-2r4h and fix it if it is affected.

What it is: GHSA-28hp-fgcr-2r4h is a cross-site scripting vulnerability in angular, published on 27 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-28hp-fgcr-2r4h in the wild and no public exploit code.

Affected packages and fixed versions:
- angular (npm): affected all versions; fixed in 1.6.0
- angular (npm): affected all versions; fixed in 1.6.0

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/GHSA-28hp-fgcr-2r4h/ (Markdown: https://insights.sbomify.com/GHSA-28hp-fgcr-2r4h/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-28hp-fgcr-2r4h

---
From sbomify Insights: https://insights.sbomify.com/GHSA-28hp-fgcr-2r4h/
Summaries are generated and may contain mistakes; the official description above is the record.