# CVE-2019-4131: Server-side request forgery in Monitoring

> A remote attacker can induce server-side DNS lookups of arbitrary domains in IBM Application Performance Management, potentially exposing internal network information.

- **Severity:** Medium 5.3 (`CVSS:3.0/UI:N/A:N/I:L/S:U/PR:N/C:N/AC:L/AV:N/RL:O/E:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9j36-8x69-cj22

## What is CVE-2019-4131?

CVE-2019-4131 is a medium-severity server-side request forgery vulnerability in IBM Monitoring, published on 11 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Application Performance Management (IBM Monitoring 8.1.4) could allow a remote attacker to induce the application to perform server-side DNS lookups of arbitrary domain names. IBM X-Force ID: 158270.

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

It affects 1 product.


Products: Ibm Cloud Application Performance Management.

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

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

## Is CVE-2019-4131 being exploited?

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

## Other vulnerabilities in IBM Monitoring

- [CVE-2020-4719](https://insights.sbomify.com/CVE-2020-4719/): Server-side request forgery in Cloud APM (medium 4.9)
- [CVE-2020-4725](https://insights.sbomify.com/CVE-2020-4725/): Cross-site scripting in Cloud APM (medium 4.3)
- [CVE-2020-4726](https://insights.sbomify.com/CVE-2020-4726/): Information disclosure in Cloud APM (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-4131 is a medium-severity server-side request forgery vulnerability in IBM Monitoring, published on 11 Jul 2019. 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-4131 in the wild and no public exploit code.

Affected product: IBM Monitoring. 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-2019-4131/ (Markdown: https://insights.sbomify.com/CVE-2019-4131/index.md)
```

## Sources

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

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