cve.bz

CAPEC-37

Retrieve Embedded Sensitive Data

Very High severityHigh likelihoodDetailed pattern

An attacker examines a target system to find sensitive data that has been embedded within it. This information can reveal confidential contents, such as account numbers or individual keys/credentials that can be used as an intermediate step in a larger attack.

On this page

Ask an AI about this attack pattern

Show the promptExplain the attack pattern CAPEC-37: Retrieve Embedded Sensitive Data: how it unfolds, what it needs and how to prevent and detect it in my systems. Use https://capec.mitre.org/data/definitions/37.html and https://cve.bz/cve/capec/37?via=ask-ai-copy, which lists recent CVEs with the weaknesses it exploits. Cite the sources.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this attack pattern's id and public links.

How the attack unfolds

  1. Explore

    The attacker looks for a way in.

    1. [Identify Target] Attacker identifies client components to extract information from. These may be binary executables, class files, shared libraries (e.g., DLLs), configuration files, or other system files.

      2 techniques
      • Binary file extraction. The attacker extracts binary files from zips, jars, wars, PDFs or other composite formats.
      • Package listing. The attacker uses a package manifest provided with the software installer, or the filesystem itself, to identify component files suitable for attack.
  2. Exploit

    They carry out the attack.

    1. [Retrieve Embedded Data] The attacker then uses a variety of techniques, such as sniffing, reverse-engineering, and cryptanalysis to retrieve the information of interest.

      4 techniques
      • API Profiling. The attacker monitors the software's use of registry keys or other operating system-provided storage locations that can contain sensitive information.
      • Execution in simulator. The attacker physically removes mass storage from the system and explores it using a simulator, external system, or other debugging harness.
      • Common decoding methods. The attacker applies methods to decode such encodings and compressions as Base64, unzip, unrar, RLE decoding, gzip decompression and so on.
      • Common data typing. The attacker looks for common file signatures for well-known file types (JPEG, TIFF, ASN.1, LDIF, etc.). If the signatures match, they attempt decoding in that format.

Prerequisites

  • In order to feasibly execute this type of attack, some valuable data must be present in client software.

  • Additionally, this information must be unprotected, or protected in a flawed fashion, or through a mechanism that fails to resist reverse engineering, statistical, or other attack.

Skills required

  • Medium skill

    The attacker must possess knowledge of client code structure as well as ability to reverse-engineer or decompile it or probe it in other ways. This knowledge is specific to the technology and language used for the client distribution

Resources required

  • The attacker must possess access to the system or code being exploited. Such access, for this set of attacks, will likely be physical. The attacker will make use of reverse engineering technologies, perhaps for data or to extract functionality from the binary. Such tool use may be as simple as "Strings" or a hex editor. Removing functionality may require the use of only a hex editor, or may require aspects of the toolchain used to construct the application: for instance the Adobe Flash development environment. Attacks of this nature do not require network access or undue CPU, memory, or other hardware-based resources.

Consequences

What a successful attack can lead to
ImpactAffectsNote
Read DataConfidentiality
Modify DataIntegrity
Gain PrivilegesConfidentiality, Access Control, Authorization

Weaknesses it exploits

  • CWE-226 Sensitive Information in Resource Not Removed Before Reuse
  • CWE-311 Missing Encryption of Sensitive Data
  • CWE-312 Cleartext Storage of Sensitive Information
  • CWE-314 Cleartext Storage in the Registry
  • CWE-315 Cleartext Storage of Sensitive Information in a Cookie
  • CWE-318 Cleartext Storage of Sensitive Information in Executable
  • CWE-525 Use of Web Browser Cache Containing Sensitive Information
  • CWE-1239 Improper Zeroization of Hardware Register
  • CWE-1258 Exposure of Sensitive System Information Due to Uncleared Debug Information
  • CWE-1266 Improper Scrubbing of Sensitive Data from Decommissioned Device
  • CWE-1272 Sensitive Information Uncleared Before Debug/Power State Transition
  • CWE-1278 Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
  • CWE-1301 Insufficient or Incomplete Data Removal within Hardware Component
  • CWE-1330 Remanent Data Readable after Memory Erase

Recent CVEs with these weaknesses

  1. 6.3CVE-2026-105813

    Cleartext storage of sensitive information in Ivanti UWM before version 2026.4 allows a local authenticated attacker to retrieve another local user's session token.

  2. 7.1CVE-2026-115340

    Progress Software WS_FTP Server versions prior to 2025.0.5 on Windows may write sensitive user credential and session data to a temporary file during file transfer operations.

  3. 6.0CVE-2026-112168

    The Magistra software uses weak custom encryption, relies on an outdated compression algorithm to protect the database, and contains embedded secrets.

  4. –CVE-2026-50204

    Apache Airflow's audit log stored Connection and Variable secret values in cleartext in the `Log.extra` column because the secrets masker matched only on configured sensitive key names. An authenticated low-privilege user with read access …

  5. 7.5CVE-2026-68933

    Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, public dashboard passwords were stored in plaintext, accepted through a URL query parameter, and…

  6. 3.7CVE-2026-5345

    HCL AION is affected by a missing encryption vulnerability in a second WebSocket connection defined in the GenAI web interface. The connection used the unencrypted WebSocket protocol (ws://test) instead of an encrypted (wss://) channel. Th…

  7. 5.4CVE-2026-35110

    HCL AION is affected by a vulnerability where encrypted (HTTPS) communication was not enforced for all requests. Data may be transmitted over unencrypted connections and intercepted by an attacker on the network, potentially resulting in u…

  8. 3.7CVE-2026-21849

    HCL AION is affected by a missing encryption vulnerability in the WebSocket connection set up by the GenAI web interface. The connection used the unencrypted WebSocket protocol (ws://localhost:8000) instead of an encrypted (wss://) channel…

The newest records naming one of them. Each weakness's page lists them all.

Part of

Examples

Using a tool such as 'strings' or similar to pull out text data, perhaps part of a database table, that exten…

Using a tool such as 'strings' or similar to pull out text data, perhaps part of a database table, that extends beyond what a particular user's purview should be.

An attacker can also use a decompiler to decompile a downloaded Java applet in order to look for information …

An attacker can also use a decompiler to decompile a downloaded Java applet in order to look for information such as hardcoded IP addresses, file paths, passwords or other such contents.

Attacker uses a tool such as a browser plug-in to pull cookie or other token information that, from a previou…

Attacker uses a tool such as a browser plug-in to pull cookie or other token information that, from a previous user at the same machine (perhaps a kiosk), allows the attacker to log in as the previous user.

MITRE's words, unchanged: CAPEC-37 at MITRE. CAPEC is Copyright © 2007–2026, The MITRE Corporation, used under the CAPEC terms of use: “The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use Common Attack Pattern Enumeration and Classification (CAPEC™) for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE’s copyright designation and this license in any such copy.” CAPEC and the CAPEC logo are trademarks of The MITRE Corporation. Credits. All attack patterns.