CVE-2018-9838
highPriorität · verfolgen · 40EPSS 0.042 · 91. PerzentilEURUUSEPSS · bewertet 2026-10-27
The caml_ba_deserialize function in byterun/bigarray.c in the standard library in OCaml 4.06.0 has an integer overflow which, in situations where marshalled data is accepted from an untrusted source, allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via a crafted object.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · high–critical · 7.5–9.8
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (8)
Betroffene Produkte und Versionsbereiche.
Advisories (1)
Hersteller- und Ökosystem-Meldungen dazu.
- OSEC-2018-01An integer overflow in the `bigarray` serialization module leads to arbitrary code execution2018-04-06vendor · osvUS
## Bug description The bigarray module in all recent ocaml versions is capable of reading in serialized (marshalled) objects from a external source which is often used for network operations and interprocess communication. byterun/bigarray.c Line 458 in ea60609 ```C b->data = malloc(elt_size * num_elts); ``` A integer overflow vulnerability allows under certain circumstances an remote attacker to input a corrupt object and edit arbitrary addresses in the processes memory which leads over common techniques (in this take libc one gadget but any rop gadget or got table vector would work) to arbitrary memory access (!) and in the course also arbitrary code execution Please check the writeup.pdf for more details !! In variations of this the exploit is usable in all ocaml versions we tested no matter if compiled to binary or intepreted (!) ## Steps to reproduce Check out the attached archive and run the makefile (or use the precompile executable) the exploit can be run by executing exploit.py (python2.7 and pwntools are required) The last step of code execution is using a one-gadget attack technique and is specific to the glibc version in use (e.g. tested is debian glibc 2.24-11+deb9u1) but can with minimal amount of work be ported to any libc version on any patch level to our knowledge Of course you can also use the exploit.py to write your own version of exploit ## Additional information This Vulnerability in ocaml was discovered by me (maximilian.tschirschnitz@gmx.de) and the exploit collaboratly developed with (philipp.hagenlocher@tum.de) For illustration purposes it was packaged as security challenge to demonstrate the impact of the issue (see writeup.pdf)
auch bekannt als (4)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (7)
Externe Belege — Patches, Meldungen, Analysen.
- https://caml.inria.fr/mantis/view.php?id=7765cnnvd
- https://packetstormsecurity.com/files/158616/Gentoo-Linux-Security-Advisory-202007-48.htmlcnnvd
- https://security.gentoo.org/glsa/202007-48cnnvd
- https://caml.inria.fr/mantis/view.php?id=7765enisa_euvd
- https://security.gentoo.org/glsa/202007-48enisa_euvd
- https://caml.inria.fr/mantis/view.php?id=7765Issue TrackingVendor Advisorynvd
- https://security.gentoo.org/glsa/202007-48nvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan