Technique:Identifying C++ utility libraries
Appearance
| On this wiki | Facts · Code · Notes · Topics |
|---|
How to tell which header-only or embedded C++ library (JSON parsers, Boost, embedded browsers) a native binary carries, from exception texts, error tables, version macros and DLL names, with a table linking to each library page.
Method
- Search strings for characteristic error text. 2. Look at RTTI/mangled namespaces. 3. Look for companion DLLs. Header-only libraries have no DLL, so strings are the main evidence.
Table
| Library | Fingerprint |
|---|---|
| Library:JSON for Modern C++ | [json.exception.parse_error.101] prefixes; nlohmann::json_abi_v3_x_y
|
| Library:RapidJSON | Missing a comma or '}' after an object member.; rapidjson:: RTTI
|
| Library:simdjson | TAPE_ERROR: The JSON document has an improper structure; SIMDJSON_VERSION
|
| Library:Boost | boost:: RTTI; boost_*-vc143-mt-x64-1_xx.dll; asio.misc
|
| Library:Chromium Embedded Framework | libcef.dll, cef_version_info export, --type=renderer subprocesses
|
| Library:WebView2 | WebView2Loader.dll, CreateCoreWebView2EnvironmentWithOptions, msedgewebview2.exe
|
| Library:Electron | Chromium plus Node.js, app.asar |
| Library:Qt | moc meta-object tables; Qt WebEngine adds QtWebEngineProcess.exe |
For compression, crypto and media libraries see Technique:Identifying compression libraries in binaries, Technique:Identifying cryptographic libraries, Technique:Identifying media libraries in binaries.
Pitfalls
Several JSON libraries can coexist (engine plus launcher plus SDK). Identify each hit separately and note where the strings sit.