mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2025-01-07 08:34:59 +00:00
9ed20568e7
This commit introduces basic annotations for `std::basic_string`,
mirroring the approach used in `std::vector` and `std::deque`.
Initially, only long strings with the default allocator will be
annotated. Short strings (_SSO - short string optimization_) and strings
with non-default allocators will be annotated in the near future, with
separate commits dedicated to enabling them. The process will be similar
to the workflow employed for enabling annotations in `std::deque`.
**Please note**: these annotations function effectively only when libc++
and libc++abi dylibs are instrumented (with ASan). This aligns with the
prevailing behavior of Memory Sanitizer.
To avoid breaking everything, this commit also appends
`_LIBCPP_INSTRUMENTED_WITH_ASAN` to `__config_site` whenever libc++ is
compiled with ASan. If this macro is not defined, string annotations are
not enabled. However, linking a binary that does **not** annotate
strings with a dynamic library that annotates strings, is not permitted.
Originally proposed here: https://reviews.llvm.org/D132769
Related patches on Phabricator:
- Turning on annotations for short strings:
https://reviews.llvm.org/D147680
- Turning on annotations for all allocators:
https://reviews.llvm.org/D146214
This PR is a part of a series of patches extending AddressSanitizer C++
container overflow detection capabilities by adding annotations, similar
to those existing in `std::vector` and `std::deque` collections. These
enhancements empower ASan to effectively detect instances where the
instrumented program attempts to access memory within a collection's
internal allocation that remains unused. This includes cases where
access occurs before or after the stored elements in `std::deque`, or
between the `std::basic_string`'s size (including the null terminator)
and capacity bounds.
The introduction of these annotations was spurred by a real-world
software bug discovered by Trail of Bits, involving an out-of-bounds
memory access during the comparison of two strings using the
`std::equals` function. This function was taking iterators
(`iter1_begin`, `iter1_end`, `iter2_begin`) to perform the comparison,
using a custom comparison function. When the `iter1` object exceeded the
length of `iter2`, an out-of-bounds read could occur on the `iter2`
object. Container sanitization, upon enabling these annotations, would
effectively identify and flag this potential vulnerability.
This Pull Request introduces basic annotations for `std::basic_string`.
Long strings exhibit structural similarities to `std::vector` and will
be annotated accordingly. Short strings are already implemented, but
will be turned on separately in a forthcoming commit. Look at [a
comment](https://github.com/llvm/llvm-project/pull/72677#issuecomment-1850554465)
below to read about SSO issues at current moment.
Due to the functionality introduced in
[D132522](dd1b7b797a),
the `__sanitizer_annotate_contiguous_container` function now offers
compatibility with all allocators. However, enabling this support will
be done in a subsequent commit. For the time being, only strings with
the default allocator will be annotated.
If you have any questions, please email:
- advenam.tacet@trailofbits.com
- disconnect3d@trailofbits.com
56 lines
1.9 KiB
Plaintext
56 lines
1.9 KiB
Plaintext
//===----------------------------------------------------------------------===//
|
|
//
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#ifndef _LIBCPP___CONFIG_SITE
|
|
#define _LIBCPP___CONFIG_SITE
|
|
|
|
#cmakedefine _LIBCPP_ABI_VERSION @_LIBCPP_ABI_VERSION@
|
|
#cmakedefine _LIBCPP_ABI_NAMESPACE @_LIBCPP_ABI_NAMESPACE@
|
|
#cmakedefine _LIBCPP_ABI_FORCE_ITANIUM
|
|
#cmakedefine _LIBCPP_ABI_FORCE_MICROSOFT
|
|
#cmakedefine _LIBCPP_HAS_NO_THREADS
|
|
#cmakedefine _LIBCPP_HAS_NO_MONOTONIC_CLOCK
|
|
#cmakedefine _LIBCPP_HAS_MUSL_LIBC
|
|
#cmakedefine _LIBCPP_HAS_THREAD_API_PTHREAD
|
|
#cmakedefine _LIBCPP_HAS_THREAD_API_EXTERNAL
|
|
#cmakedefine _LIBCPP_HAS_THREAD_API_WIN32
|
|
#cmakedefine _LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS
|
|
#cmakedefine _LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS
|
|
#cmakedefine _LIBCPP_NO_VCRUNTIME
|
|
#cmakedefine _LIBCPP_TYPEINFO_COMPARISON_IMPLEMENTATION @_LIBCPP_TYPEINFO_COMPARISON_IMPLEMENTATION@
|
|
#cmakedefine _LIBCPP_HAS_NO_FILESYSTEM
|
|
#cmakedefine _LIBCPP_HAS_NO_RANDOM_DEVICE
|
|
#cmakedefine _LIBCPP_HAS_NO_LOCALIZATION
|
|
#cmakedefine _LIBCPP_HAS_NO_WIDE_CHARACTERS
|
|
#cmakedefine _LIBCPP_HAS_NO_STD_MODULES
|
|
#cmakedefine _LIBCPP_HAS_NO_TIME_ZONE_DATABASE
|
|
#cmakedefine _LIBCPP_INSTRUMENTED_WITH_ASAN
|
|
|
|
// PSTL backends
|
|
#cmakedefine _LIBCPP_PSTL_CPU_BACKEND_SERIAL
|
|
#cmakedefine _LIBCPP_PSTL_CPU_BACKEND_THREAD
|
|
#cmakedefine _LIBCPP_PSTL_CPU_BACKEND_LIBDISPATCH
|
|
|
|
// Hardening.
|
|
#cmakedefine _LIBCPP_HARDENING_MODE_DEFAULT @_LIBCPP_HARDENING_MODE_DEFAULT@
|
|
|
|
// __USE_MINGW_ANSI_STDIO gets redefined on MinGW
|
|
#ifdef __clang__
|
|
# pragma clang diagnostic push
|
|
# pragma clang diagnostic ignored "-Wmacro-redefined"
|
|
#endif
|
|
|
|
@_LIBCPP_ABI_DEFINES@
|
|
@_LIBCPP_EXTRA_SITE_DEFINES@
|
|
|
|
#ifdef __clang__
|
|
# pragma clang diagnostic pop
|
|
#endif
|
|
|
|
#endif // _LIBCPP___CONFIG_SITE
|