CVE-2016-4303: The parse_string function in cjson.c in the cJSON library mishandles UTF8/16 strings, which allows remote attackers to cause a denial of…
Noroxi assessment
Priority: Plan (action score 41/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 6.9% (FIRST EPSS); higher than 94.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: iperf3 (Debian:12) 3.1.3-1; iperf3 (Debian:8) 3.0.7-1+deb8u1; iperf (openSUSE:Tumbleweed) 3.1.3-1.3.
Add it to your regular patch cycle. Upgrade to iperf3 (Debian:12) 3.1.3-1; iperf3 (Debian:8) 3.0.7-1+deb8u1; iperf (openSUSE:Tumbleweed) 3.1.3-1.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The parse_string function in cjson.c in the cJSON library mishandles UTF8/16 strings, which allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a non-hex character in a JSON string, which triggers a heap-based buffer overflow.
- Published
- Sep 26, 2016
- Updated
- Jun 16, 2026
- EPSS
- 6.9% · 94th percentile
- CWE
- CWE-120
Report tools
Action score
41
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| es | iperf3 | cpe:2.3:a:es:iperf3 |
| novell | suse package hub for suse linux enterprise | cpe:2.3:a:novell:suse_package_hub_for_suse_linux_enterprise |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| opensuse | opensuse | cpe:2.3:o:opensuse:opensuse |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- es iperf33.0 and later · before 3.0.12
- es iperf33.1 and later · before 3.1.3
- novell suse package hub for suse linux enterprise12
- opensuse leap42.1
- opensuse opensuse13.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | iperf3 | before 3.1.3-1 | 3.1.3-1 |
| Debian:8 | iperf3 | before 3.0.7-1+deb8u1 | 3.0.7-1+deb8u1 |
| openSUSE:Tumbleweed | iperf | before 3.1.3-1.3 | 3.1.3-1.3 |
| SUSE:Package Hub 12 | iperf | before 3.1.3-6.1 | 3.1.3-6.1 |
Same product
es: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-54351In iperf before 3.19.1, net.c has a buffer overflow when --skip-rx-copy is used (for MSG_TRUNC in recv).40Plan
- CVE-2025-54349In iperf before 3.19.1, iperf_auth.c has an off-by-one error and resultant heap-based buffer overflow.40Plan
- CVE-2023-38403iperf3 before 3.14 allows peers to cause an integer overflow and heap corruption via a crafted length field.31Monitor
Published before and after this one in the same product
- Later →CVE-2023-7250Mar 18, 2024 · Iperf3: possible denial of service21Monitor
- Later →CVE-2024-26306May 14, 2024 · iPerf3 before 3.17, when used with OpenSSL before 3.2.0 as a server with RSA authentication, allows a timing side channel in RSA decryption…23Monitor
- Later →CVE-2024-53580Dec 18, 2024 · iperf v3.17.1 was discovered to contain a segmentation violation via the iperf_exchange_parameters() function.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:iperf3 | 3.1.3-1 · Debian:12 | Package registry (OSV) |
| opensuse:iperf | 3.1.3-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:iperf | 3.1.3-6.1 · SUSE:Package Hub 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- lists.opensuse.org/opensuse-updates/2016-08/msg00090.html
- software.es.net/iperf/news.html#security-issue-iperf-3-1-3-iperf-3-0-12-released
- github.com/esnet/iperf/commit/91f2fa59e8ed80dfbf400add0164ee0e508e412a
- lists.debian.org/debian-lts-announce/2020/01/msg00023.html
- raw.githubusercontent.com/esnet/security/master/cve-2016-4303/esnet-secadv-2016-0001.txt.asc
Vendor advisories and official records. Exploit/PoC links are deliberately left out.