# CVE-2025-43015: Misconfiguration in RubyMine

> Remote interpreter in RubyMine listens on all interfaces, potentially exposing services to unauthorized network access.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-7g9q-ww3r-j77g

## What is CVE-2025-43015?

CVE-2025-43015 is a high-severity vulnerability in JetBrains RubyMine, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In JetBrains RubyMine before 2025.1 remote Interpreter overwrote ports to listen on all interfaces

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2025-43015?

It affects 1 product.


Products: Jetbrains Rubymine.

## How do I fix CVE-2025-43015?

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

## Is CVE-2025-43015 being exploited?

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

## Other vulnerabilities in JetBrains RubyMine

- [CVE-2021-37543](https://insights.sbomify.com/CVE-2021-37543/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43015 and fix it if it is affected.

What it is: CVE-2025-43015 is a high-severity vulnerability in JetBrains RubyMine, published on 17 Apr 2025. 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-2025-43015 in the wild and no public exploit code.

Affected product: JetBrains RubyMine. 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-2025-43015/ (Markdown: https://insights.sbomify.com/CVE-2025-43015/index.md)
```

## Sources

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

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