CoAPthon3 vulnerable to Deserialization of Untrusted Data

published 2019-04-02 7y ago modified 2026-06-17 4mo ago also GHSA-c6fm-rgw4-8q73 , PYSEC-2019-166 , EUVD-2019-0029

cvss: 7.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

The Serialize.deserialize() method in CoAPthon3 1.0 and 1.0.1 mishandles certain exceptions, leading to a denial of service in applications that use this library (e.g., the standard CoAP server, CoAP client, example collect CoAP server and client) when they receive crafted CoAP messages.

Is CVE-2018-12679 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

github.com https://github.com/Tanganelli/CoAPthon3/issues/16 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
pypi	coapthon3	<=1.0.1 >=1.0	no fix listed

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

github.com /Tanganelli/CoAPthon3/issues/16
web, exploit, issue-tracking, third-party-advisory, report
nvd.nist.gov /vuln/detail/CVE-2018-12679
advisory
github.com /Tanganelli/CoAPthon3
package
github.com /advisories/GHSA-c6fm-rgw4-8q73
advisory
github.com /pypa/advisory-database/tree/main/vulns/coapthon3/PYSEC-2019-166.yaml
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.