high
7.5
CWE
119
Advisory Published
CVE Published
Updated

CVE-2012-6089: Buffer Overflow

First published: Thu Jan 03 2013(Updated: )

Changelog for pl-6.2.5 reads: * FIXED: Possible buffer overrun in patch canonisation code. Pushes pointers on an automatic array without checking for overflow. Can be used for DoS attacks. Will be extremely hard to make it execute arbitrary code. * SECURITY: Possible buffer overflows when expanding file-names with long paths. Affects expand_file_name/2. Can lead to crashes (DoS attacks) and possibly execution of arbitrary code if an attacker can control the names of the files searched for, e.g., if expand_file_name/2 is used in a directory to which an attacker can upload files for which he can control the name. These fixes are implemented by upstream commits: From a9a6fc8a2a9cf3b9154b490a4b1ffaa8be4d723c Mon Sep 17 00:00:00 2001 From: Jan Wielemaker <J.Wielemaker.nl> Date: Sun, 16 Dec 2012 18:13:17 +0100 Subject: [PATCH] FIXED: Possible buffer overrun in patch canonisation code. Pushes pointers on an automatic array without checking for overflow. Can be used for DoS attacks. Will be extremely hard to make it execute arbitrary code. From b2c88972e7515ada025e97e7d3ce3e34f81cf33e Mon Sep 17 00:00:00 2001 From: Jan Wielemaker <J.Wielemaker.nl> Date: Sun, 16 Dec 2012 17:29:37 +0100 Subject: [PATCH] SECURITY: Possible buffer overflows when expanding file-names with long paths. Affects expand_file_name/2. Can lead to crashes (DoS attacks) and possibly execution of arbitrary code if an attacker can control the names of the files searched for, e.g., if expand_file_name/2 is used in a directory to which an attacker can upload files for which he can control the name. I believe the vulnerabilities exist in older pl.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/SWI-Prolog<6.3.7
6.3.7
redhat/SWI-Prolog<6.2.5
6.2.5
SWI-Prolog<=6.2.4
SWI-Prolog=5.6.50
SWI-Prolog=5.6.51
SWI-Prolog=5.6.52
SWI-Prolog=5.6.53
SWI-Prolog=5.6.54
SWI-Prolog=5.6.55
SWI-Prolog=5.6.56
SWI-Prolog=5.6.57
SWI-Prolog=5.6.58
SWI-Prolog=5.6.59
SWI-Prolog=5.6.61
SWI-Prolog=5.6.62
SWI-Prolog=5.6.63
SWI-Prolog=5.6.64
SWI-Prolog=5.8.0
SWI-Prolog=5.8.1
SWI-Prolog=5.8.2
SWI-Prolog=5.8.3
SWI-Prolog=5.10.0
SWI-Prolog=5.10.1
SWI-Prolog=5.10.2
SWI-Prolog=5.10.3
SWI-Prolog=5.10.4
SWI-Prolog=5.10.5
SWI-Prolog=6.0.0
SWI-Prolog=6.0.1
SWI-Prolog=6.0.2
SWI-Prolog=6.2.0
SWI-Prolog=6.2.1
SWI-Prolog=6.2.2
SWI-Prolog=6.2.3
SWI-Prolog=6.3.0
SWI-Prolog=6.3.1
SWI-Prolog=6.3.2
SWI-Prolog=6.3.3
SWI-Prolog=6.3.4
SWI-Prolog=6.3.5
SWI-Prolog=6.3.6

Remedy

http://www.swi-prolog.org/git/pl.git/commit/a9a6fc8a2a9cf3b9154b490a4b1ffaa8be4d723c

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2012-6089?

    The severity of CVE-2012-6089 is medium due to the potential for denial-of-service attacks rather than arbitrary code execution.

  • How do I fix CVE-2012-6089?

    To fix CVE-2012-6089, upgrade to SWI-Prolog version 6.3.7 or later.

  • Which versions are affected by CVE-2012-6089?

    CVE-2012-6089 affects SWI-Prolog versions up to 6.2.5 and earlier.

  • Can CVE-2012-6089 lead to remote code execution?

    CVE-2012-6089 is primarily a denial-of-service vulnerability and is extremely hard to exploit for arbitrary code execution.

  • What type of attack can CVE-2012-6089 enable?

    CVE-2012-6089 can enable denial-of-service attacks due to a possible buffer overrun.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203