# CVE-2015-3977: Memory corruption in n/a

> Remote authenticated attackers can execute arbitrary code or cause denial of service via a crafted HART reply in Schneider Electric IMT25 Magnetic Flow DTM.

- **Severity:** High 7.7 (`AV:A/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2pwf-vfjj-694r

## What is CVE-2015-3977?

CVE-2015-3977 is a high-severity memory corruption vulnerability in n/a, published on 15 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in Schneider Electric IMT25 Magnetic Flow DTM before 1.500.004 for the HART Protocol allows remote authenticated users to execute arbitrary code or cause a denial of service (memory corruption) via a crafted HART reply.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2015-3977?

It affects 1 product.


Products: Schneider-Electric Imt25 Magnetic Flow Dtm.

## How do I fix CVE-2015-3977?

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

## Is CVE-2015-3977 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3977 and fix it if it is affected.

What it is: CVE-2015-3977 is a high-severity memory corruption vulnerability in n/a, published on 15 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3977 in the wild and no public exploit code.

Affected product: n/a. 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-2015-3977/ (Markdown: https://insights.sbomify.com/CVE-2015-3977/index.md)
```

## Sources

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

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