Heap-use-after-free vulnerability in igraph_pajek_yyparse

igraph Updated 02 Oct 2025

Summary

27/10/2023

Disclosed on

HIGH

Severity

Yes i

Fix available

High

Severity

Not published

CVSS Score

OSV-2023-1071: Heap-use-after-free in igraph_pajek_yyparse. Affects igraph versions >= 4f4f2e97e6dddd20081da17d4016dbcf3f573250, < c32ae3b44074c280e1a8cc3ff3fe8899040753ff. Fixed in c32ae3b44074c280e1a8cc3ff3fe8899040753ff. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

The package under scrutiny is igraph, an open-source library for creating and manipulating graphs. It provides various functionalities for graph analysis and visualization. The vulnerability affects the igraph_pajek_yyparse function, which is responsible for parsing Pajek format files. Pajek is a popular file format used for representing network data. This vulnerability allows an attacker to exploit a heap-use-after-free bug, potentially leading to arbitrary code execution or denial of service.

Vulnerability Detail

The vulnerability originates from a heap-use-after-free bug in the igraph_pajek_yyparse function. This bug occurs when the function continues to access a heap-allocated object after it has been freed. An attacker can craft a malicious Pajek format file that triggers this bug, leading to memory corruption and potentially allowing them to execute arbitrary code or crash the application. The bug was discovered through the OSS-Fuzz project and has been assigned a high severity level.

How To Fix

Minimum fixed version

c32ae3b44074c280e1a8cc3ff3fe8899040753ff

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there is no known workaround for this vulnerability. It is essential to update the igraph package to a fixed version as soon as possible.

Conclusion

In conclusion, the igraph package is vulnerable to a heap-use-after-free bug in the igraph_pajek_yyparse function. This bug can be exploited by crafting a malicious Pajek format file. It is crucial for developers to update their dependencies to include the fix and rebuild their applications. Regularly updating dependencies is recommended to stay protected against such vulnerabilities. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for igraph →