Page History

The C standard library facilities setjmp() and longjmp() can be used to simulate throwing and catching exceptions. However, these facilities bypass automatic resource management and can result in undefined behavior, commonly including resource leaks , and denial-of-service attacks.

The C++ Standard, [support.runtime], paragraph 4 [ISO/IEC 14882-2014], states the following:

The function signature longjmp(jmp_buf jbuf, int val) has more restricted behavior in this International Standard. A setjmp/longjmp call pair has undefined behavior if replacing the setjmp and longjmp by catch and throw would invoke any non-trivial destructors for any automatic objects.

...

Noncompliant Code Example

Calling longjmp() such that it would invoke a nontrivial destructor were the call replaced with a throw expression results in undefined behavior, as demonstrated in this noncompliant code example:If a throw expression would cause a nontrivial destructor to be invoked, then calling longjmp() in the same context will result in undefined behavior. In the following noncompliant code example, the call to longjmp() occurs in a context with a local Counter object. Since this object’s destructor is nontrivial, undefined behavior results.

#include <csetjmp>
#include <iostream>

static jmp_buf env;

struct Counter {
  static int Instancesinstances;
  Counter() { ++Instancesinstances; }
  ~Counter() { --Instancesinstances; }
};

int Counter::Instancesinstances = 0;

void f() {
  Counter c;
  std::cout << "f(): Instances: " << Counter::Instancesinstances << std::endl;
  std::longjmp(env, 1);
}

int main() {
  std::cout << "Before setjmp(): Instances: " << Counter::Instancesinstances << std::endl;
  if (setjmp(env) == 0) {
    f();
  } else {
    std::cout << "From longjmp(): Instances: " << Counter::Instancesinstances << std::endl;
  }
  std::cout << "After longjmp(): Instances: " << Counter::Instancesinstances << std::endl;
}

Implementation Details

The above code produces the following results when compiled with Clang 3.5 8 for Linux, demonstrating that the undefined behavior in this instance is to fail program, on this platform, fails to destroy the local Counter instance when the execution of f() is terminated:. This is permissible as the behavior is undefined.

Before setjmp(): Instances: 0
f(): Instances: 1
From longjmp(): Instances: 1
After longjmp(): Instances: 1

...

This compliant solution replaces the calls to setjmp() and longjmp() with a throw expression and a catch statement:.

#include <iostream>

struct Counter {
  static int Instancesinstances;
  Counter() { ++Instancesinstances; }
  ~Counter() { --Instancesinstances; }
};

int Counter::Instancesinstances = 0;

void f() {
  Counter c;
  std::cout << "f(): Instances: " << Counter::Instancesinstances << std::endl;
  throw "Exception";
}

int main() {
  std::cout << "Before throw: Instances: " << Counter::Instancesinstances << std::endl;
  try {
    f();
  } catch (const char *E) {
    std::cout << "From catch: Instances: " << Counter::Instancesinstances << std::endl;
  }
  std::cout << "After catch: Instances: " << Counter::Instancesinstances << std::endl;
}

which This solution produces the following output:.

Before throw: Instances: 0
f(): Instances: 1
From catch: Instances: 0
After catch: Instances: 0

...

Using setjmp() and longjmp() could lead to a denial-of-service attack due to resources not being properly destroyed.

Automated Detection

Related Vulnerabilities

Search for other vulnerabilities resulting from the violation of this rule on the CERT website.

Bibliography

...

[Henricson

97

1997]

Rule 13.3,

"

Do not use setjmp() and longjmp()

"

...

[ISO/IEC 14882-2014]	Subclause 18.10, "Other Runtime Support"

...

Image Modified Image Modified Image Modified