CWE-209
AllowedGeneration of Error Message Containing Sensitive Information
Abstraction: Base · Status: Draft
The product generates an error message that includes sensitive information about its environment, users, or associated data.
833 vulnerabilities reference this CWE, most recent first.
GHSA-GHGP-42HG-J6P2
Vulnerability from github – Published: 2026-03-13 21:31 – Updated: 2026-03-13 21:31IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 could allow a remote attacker to obtain sensitive information when detailed technical error messages are returned. This information could be used in further attacks against the system.
{
"affected": [],
"aliases": [
"CVE-2025-13726"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-13T19:53:48Z",
"severity": "MODERATE"
},
"details": "IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 could allow a remote attacker to obtain sensitive information when detailed technical error messages are returned. This information could be used in further attacks against the system.",
"id": "GHSA-ghgp-42hg-j6p2",
"modified": "2026-03-13T21:31:45Z",
"published": "2026-03-13T21:31:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-13726"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7263391"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GJ6X-Q8RH-WJ6X
Vulnerability from github – Published: 2026-02-26 22:48 – Updated: 2026-02-26 22:48Summary
Multiple HTTP handlers in Curio passed raw database error messages to HTTP clients via http.Error(). When the PostgreSQL/YugabyteDB driver (pgx) returned errors, these could contain the database connection string — including hostname, port, username, and password. Additionally, the internal connection string was constructed with the plaintext password embedded in the URL, which was also included in startup error messages and could surface in logs.
Details
Three components were affected:
-
PDP handlers (
pdp/handlers.go) — 18+ HTTP error paths passederr.Error()directly to HTTP responses. While these endpoints require ECDSA JWT authentication, an authenticated client (e.g., a FilPay service) that triggered a database error would receive the raw pgx error in the HTTP response body. Present since PDP was introduced in v1.25.1. -
Market mk12 deal status (
market/mk12/mk12_utils.go) — TheGetDealStatushandler includederr.Error()in error responses:"failed to query the db for deal status: %s". Present since v1.24.3. -
Market mk20 auth middleware (
market/mk20/http/http.go) — Authentication error responses includederr.Error(), potentially leaking database error details during auth flows. Present since v1.27.2.
Root Cause
The database connection string was constructed as:
postgresql://username:password@host:port/database?...
The plaintext password was embedded directly in the URL. When pgx returned connection or query errors, the error text could contain fragments of this connection string. HTTP handlers forwarded these errors verbatim to clients.
Impact
An attacker with network access to Curio's PDP or Market HTTP endpoints and valid authentication credentials could intentionally trigger database errors (e.g., by sending malformed requests that cause SQL failures) and extract the YugabyteDB connection credentials from the error response. With these credentials, the attacker could directly access the database, which serves as Curio's control plane.
Per Curio's security boundary documentation, these endpoints are expected to be on a trusted network. However, defense-in-depth requires that credentials are never exposed through HTTP responses regardless of network trust assumptions.
Remediation (PR #919)
-
Connection string password masking: The password in the connection string is replaced with
********. The real password is set separately viacfg.ConnConfig.Password, so it never appears in error messages or logs. -
HTTP handler sanitization: All affected handlers now log the detailed error server-side and return a generic error message to the HTTP client.
-
Error filter (
errFilter): A new function in the database layer detects and redacts any error messages containing keywords like "password", "host", "port", or "://" before they can propagate. -
Prometheus metrics cleanup: Database connection metrics that could expose connection details were removed from the metrics endpoint.
-
Security boundary documentation: A new section documents what Curio expects operators to secure.
Resources
- Fix: https://github.com/filecoin-project/curio/pull/919
- Patched release: v1.27.3-rc2
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.27.2"
},
"package": {
"ecosystem": "Go",
"name": "github.com/filecoin-project/curio"
},
"ranges": [
{
"events": [
{
"introduced": "1.24.3"
},
{
"fixed": "1.27.3-rc2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-209",
"CWE-532"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-26T22:48:00Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "## Summary\n\nMultiple HTTP handlers in Curio passed raw database error messages to HTTP clients via `http.Error()`. When the PostgreSQL/YugabyteDB driver (pgx) returned errors, these could contain the database connection string \u2014 including hostname, port, username, and password. Additionally, the internal connection string was constructed with the plaintext password embedded in the URL, which was also included in startup error messages and could surface in logs.\n\n## Details\n\nThree components were affected:\n\n1. **PDP handlers** (`pdp/handlers.go`) \u2014 18+ HTTP error paths passed `err.Error()` directly to HTTP responses. While these endpoints require ECDSA JWT authentication, an authenticated client (e.g., a FilPay service) that triggered a database error would receive the raw pgx error in the HTTP response body. Present since PDP was introduced in v1.25.1.\n\n2. **Market mk12 deal status** (`market/mk12/mk12_utils.go`) \u2014 The `GetDealStatus` handler included `err.Error()` in error responses: `\"failed to query the db for deal status: %s\"`. Present since v1.24.3.\n\n3. **Market mk20 auth middleware** (`market/mk20/http/http.go`) \u2014 Authentication error responses included `err.Error()`, potentially leaking database error details during auth flows. Present since v1.27.2.\n\n### Root Cause\n\nThe database connection string was constructed as:\n```\npostgresql://username:password@host:port/database?...\n```\nThe plaintext password was embedded directly in the URL. When pgx returned connection or query errors, the error text could contain fragments of this connection string. HTTP handlers forwarded these errors verbatim to clients.\n\n## Impact\n\nAn attacker with network access to Curio\u0027s PDP or Market HTTP endpoints and valid authentication credentials could intentionally trigger database errors (e.g., by sending malformed requests that cause SQL failures) and extract the YugabyteDB connection credentials from the error response. With these credentials, the attacker could directly access the database, which serves as Curio\u0027s control plane.\n\nPer Curio\u0027s [security boundary documentation](https://github.com/filecoin-project/curio/blob/main/documentation/en/design/README.md#security-boundary), these endpoints are expected to be on a trusted network. However, defense-in-depth requires that credentials are never exposed through HTTP responses regardless of network trust assumptions.\n\n## Remediation (PR #919)\n\n1. **Connection string password masking:** The password in the connection string is replaced with `********`. The real password is set separately via `cfg.ConnConfig.Password`, so it never appears in error messages or logs.\n\n2. **HTTP handler sanitization:** All affected handlers now log the detailed error server-side and return a generic error message to the HTTP client.\n\n3. **Error filter (`errFilter`):** A new function in the database layer detects and redacts any error messages containing keywords like \"password\", \"host\", \"port\", or \"://\" before they can propagate.\n\n4. **Prometheus metrics cleanup:** Database connection metrics that could expose connection details were removed from the metrics endpoint.\n\n5. **Security boundary documentation:** A new section documents what Curio expects operators to secure.\n\n## Resources\n\n- Fix: https://github.com/filecoin-project/curio/pull/919\n- Patched release: v1.27.3-rc2",
"id": "GHSA-gj6x-q8rh-wj6x",
"modified": "2026-02-26T22:48:00Z",
"published": "2026-02-26T22:48:00Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/filecoin-project/curio/security/advisories/GHSA-gj6x-q8rh-wj6x"
},
{
"type": "WEB",
"url": "https://github.com/filecoin-project/curio/pull/919"
},
{
"type": "WEB",
"url": "https://github.com/filecoin-project/curio/commit/551da78e0123892600d8e6dfe9de7a579055d80b"
},
{
"type": "PACKAGE",
"url": "https://github.com/filecoin-project/curio"
},
{
"type": "WEB",
"url": "https://github.com/filecoin-project/curio/blob/main/documentation/en/design/README.md#security-boundary"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Curio exposes database credentials to users with network access through verbose HTTP error responses"
}
GHSA-GJ7G-W5GQ-HW2H
Vulnerability from github – Published: 2026-03-25 21:30 – Updated: 2026-03-25 21:30IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is affected by an information exposure vulnerability caused by overly verbose error messages
{
"affected": [],
"aliases": [
"CVE-2026-2484"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-25T21:16:41Z",
"severity": "MODERATE"
},
"details": "IBM InfoSphere Information Server\u00a011.7.0.0 through\u00a011.7.1.6\u00a0is affected by an information exposure vulnerability caused by overly verbose error messages",
"id": "GHSA-gj7g-w5gq-hw2h",
"modified": "2026-03-25T21:30:36Z",
"published": "2026-03-25T21:30:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2484"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7266767"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GM5J-3328-742C
Vulnerability from github – Published: 2025-08-05 18:30 – Updated: 2025-08-05 18:30An issue was discovered in ExonautWeb in 4C Strategies Exonaut 21.6. There are verbose error messages.
{
"affected": [],
"aliases": [
"CVE-2025-46658"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-05T16:15:29Z",
"severity": "CRITICAL"
},
"details": "An issue was discovered in ExonautWeb in 4C Strategies Exonaut 21.6. There are verbose error messages.",
"id": "GHSA-gm5j-3328-742c",
"modified": "2025-08-05T18:30:43Z",
"published": "2025-08-05T18:30:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-46658"
},
{
"type": "WEB",
"url": "https://gist.github.com/Jowu73/005ca4f85b27fb272a4e62e373341fa5"
},
{
"type": "WEB",
"url": "https://www.4cstrategies.com/solutions/exonaut"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-GMQ3-PQ82-4MJG
Vulnerability from github – Published: 2025-10-12 03:30 – Updated: 2025-10-12 03:30HCL Unica Centralized Offer Management is vulnerable to poor unhandled exceptions which exposes sensitive information. An attacker can exploit use this information to exploit known vulnerabilities launch targeted attacks, such as remote code execution or denial of service.
{
"affected": [],
"aliases": [
"CVE-2025-31998"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-10-12T03:15:34Z",
"severity": "LOW"
},
"details": "HCL Unica Centralized Offer Management is vulnerable to poor unhandled exceptions which exposes sensitive information. An attacker can exploit use this information to exploit known vulnerabilities launch targeted attacks, such as remote code execution or denial of service.",
"id": "GHSA-gmq3-pq82-4mjg",
"modified": "2025-10-12T03:30:35Z",
"published": "2025-10-12T03:30:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31998"
},
{
"type": "WEB",
"url": "https://support.hcl-software.com/csm?id=kb_article\u0026sysparm_article=KB0124422"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GPF9-442R-5M94
Vulnerability from github – Published: 2025-11-20 21:30 – Updated: 2025-11-20 21:30Debug information disclosure in the SQL error message to in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes non-admin users to acquire information about the software, PHP and database versions currently in use.
{
"affected": [],
"aliases": [
"CVE-2025-52671"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-11-20T20:16:23Z",
"severity": "MODERATE"
},
"details": "Debug information disclosure in the SQL error message to in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes non-admin users to acquire information about the software, PHP and database versions currently in use.",
"id": "GHSA-gpf9-442r-5m94",
"modified": "2025-11-20T21:30:32Z",
"published": "2025-11-20T21:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-52671"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/3403450"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GPM5-VV3G-PCJF
Vulnerability from github – Published: 2026-05-14 15:31 – Updated: 2026-05-14 15:31Vvveb before 1.0.8.3 contains an uncontrolled recursion vulnerability in the admin controller dispatch cycle where Base::init() repeatedly invokes permission() on error handlers, causing infinite recursion until PHP memory limits are exhausted. Attackers can send sustained requests to forbidden admin URLs from a low-privilege account to exhaust PHP memory on all workers and cause denial of service to legitimate traffic.
{
"affected": [],
"aliases": [
"CVE-2026-41935"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-14T15:16:46Z",
"severity": "HIGH"
},
"details": "Vvveb before 1.0.8.3 contains an uncontrolled recursion vulnerability in the admin controller dispatch cycle where Base::init() repeatedly invokes permission() on error handlers, causing infinite recursion until PHP memory limits are exhausted. Attackers can send sustained requests to forbidden admin URLs from a low-privilege account to exhaust PHP memory on all workers and cause denial of service to legitimate traffic.",
"id": "GHSA-gpm5-vv3g-pcjf",
"modified": "2026-05-14T15:31:59Z",
"published": "2026-05-14T15:31:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41935"
},
{
"type": "WEB",
"url": "https://github.com/givanz/Vvveb/commit/c766e84b479dcf1bd1f25a44e4b9c9fa450769c8"
},
{
"type": "WEB",
"url": "https://github.com/givanz/Vvveb/releases/tag/1.0.8.3"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/vvveb-uncontrolled-recursion-denial-of-service"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-GPMG-4X4G-MR5R
Vulnerability from github – Published: 2025-08-13 18:47 – Updated: 2025-08-27 14:29Background
If an error occurred when resetting a user's password using the Forgot Password option in OMERO.web, the error message displayed on the Web page can disclose information about the user.
Impact
OMERO.web before 5.29.1
Patches
User should upgrade to 5.29.2 or higher
Workarounds
Disable the Forgot password option in OMERO.web using the omero.web.show_forgot_password configuration property^1.
Thanks to Christopher Youd who reported the issue.
Open an issue in omero-web Email us at security@openmicroscopy.org
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 5.29.1"
},
"package": {
"ecosystem": "PyPI",
"name": "omero-web"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.29.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-54791"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": true,
"github_reviewed_at": "2025-08-13T18:47:35Z",
"nvd_published_at": "2025-08-13T14:15:32Z",
"severity": "MODERATE"
},
"details": "### Background\n\nIf an error occurred when resetting a user\u0027s password using the ``Forgot Password`` option in OMERO.web, the error message displayed on the Web page can disclose information about the user.\n\n### Impact\nOMERO.web before 5.29.1\n\n### Patches\nUser should upgrade to 5.29.2 or higher\n\n### Workarounds\nDisable the ``Forgot password`` option in OMERO.web using the ``omero.web.show_forgot_password`` configuration property[^1].\n\nThanks to Christopher Youd who reported the issue.\n\nOpen an issue in [omero-web](https://github.com/ome/omero-web)\nEmail us at [security@openmicroscopy.org](mailto:security@openmicroscopy.org)\n\n[^1]: https://omero.readthedocs.io/en/stable/sysadmins/config.html#omero.web.show_forgot_password",
"id": "GHSA-gpmg-4x4g-mr5r",
"modified": "2025-08-27T14:29:25Z",
"published": "2025-08-13T18:47:35Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/ome/omero-web/security/advisories/GHSA-gpmg-4x4g-mr5r"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54791"
},
{
"type": "WEB",
"url": "https://github.com/ome/omero-web/commit/8aa2789e8f759c73f1517abe9a0abd44e86644ad"
},
{
"type": "PACKAGE",
"url": "https://github.com/ome/omero-web"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "OMERO.web displays unecessary user information when requesting password reset"
}
GHSA-GQ2R-QH4M-2G7X
Vulnerability from github – Published: 2026-05-27 15:33 – Updated: 2026-05-27 18:31IBM Business Automation Workflow containers and traditional may leak information about its database structure in error messages.
{
"affected": [],
"aliases": [
"CVE-2026-1248"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-27T15:16:24Z",
"severity": "MODERATE"
},
"details": "IBM Business Automation Workflow containers and traditional\u00a0may leak information about its database structure in error messages.",
"id": "GHSA-gq2r-qh4m-2g7x",
"modified": "2026-05-27T18:31:37Z",
"published": "2026-05-27T15:33:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-1248"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7271445"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GQJ9-6PWJ-7952
Vulnerability from github – Published: 2022-05-04 00:27 – Updated: 2026-04-03 00:31Spacewalk-backend in Red Hat Network (RHN) Satellite and Proxy 5.4 includes cleartext user passwords in an error message when a system registration XML-RPC call fails, which allows remote administrators to obtain the password by reading (1) the server log and (2) an email.
{
"affected": [],
"aliases": [
"CVE-2012-0059"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-02-05T18:55:00Z",
"severity": "MODERATE"
},
"details": "Spacewalk-backend in Red Hat Network (RHN) Satellite and Proxy 5.4 includes cleartext user passwords in an error message when a system registration XML-RPC call fails, which allows remote administrators to obtain the password by reading (1) the server log and (2) an email.",
"id": "GHSA-gqj9-6pwj-7952",
"modified": "2026-04-03T00:31:08Z",
"published": "2022-05-04T00:27:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-0059"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2012-0059"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2012-0101.html"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2012-0102.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-39
- Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
- If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
- Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
Mitigation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Mitigation MIT-33
Strategy: Attack Surface Reduction
Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
Mitigation MIT-40
Strategy: Compilation or Build Hardening
Debugging information should not make its way into a production release.
Mitigation MIT-40
Strategy: Environment Hardening
Debugging information should not make its way into a production release.
Mitigation
Where available, configure the environment to use less verbose error messages. For example, in PHP, disable the display_errors setting during configuration, or at runtime using the error_reporting() function.
Mitigation
Create default error pages or messages that do not leak any information.
CAPEC-215: Fuzzing for application mapping
An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash.
CAPEC-463: Padding Oracle Crypto Attack
An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
CAPEC-54: Query System for Information
An adversary, aware of an application's location (and possibly authorized to use the application), probes an application's structure and evaluates its robustness by submitting requests and examining responses. Often, this is accomplished by sending variants of expected queries in the hope that these modified queries might return information beyond what the expected set of queries would provide.
CAPEC-7: Blind SQL Injection
Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.