# CVE-2016-3707: Security feature bypass in n/a

> Remote attackers can execute SysRq commands via crafted ICMP packets if the feature is enabled, potentially leading to privilege escalation or denial of service.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-3707, GHSA-558g-x28c-wmj6

## What is CVE-2016-3707?

CVE-2016-3707 is a high-severity vulnerability in n/a, published on 27 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The icmp_check_sysrq function in net/ipv4/icmp.c in the kernel.org projects/rt patches for the Linux kernel, as used in the kernel-rt package before 3.10.0-327.22.1 in Red Hat Enterprise Linux for Real Time 7 and other products, allows remote attackers to execute SysRq commands via crafted ICMP Echo Request packets, as demonstrated by a brute-force attack to discover a cookie, or an attack that occurs after reading the local icmp_echo_sysrq file.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-3707?

It affects 4 products.


Products: Linux Linux Kernel-Rt, Novell Suse Linux Enterprise Real Time Extension, Redhat Enterprise Linux for Real Time, Redhat Enterprise Linux for Real Time for Nfv.

## How do I fix CVE-2016-3707?

Apply the vendor's patch.

## Is CVE-2016-3707 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3707 and fix it if it is affected.

What it is: CVE-2016-3707 is a high-severity vulnerability in n/a, published on 27 Jun 2016. 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-2016-3707 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-2016-3707/ (Markdown: https://insights.sbomify.com/CVE-2016-3707/index.md)
```

## Sources

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

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