mirror of
https://github.com/elicpeter/nyx.git
synced 2026-06-06 19:35:13 +02:00
* feat: Enhance data exfiltration detection with source sensitivity gating for cookies and headers * feat: Implement cross-file data exfiltration detection with parameter-specific gate filters * feat: Add calibration tests and refine DATA_EXFIL severity scoring logic * feat: Introduce per-detector configuration for data exfiltration suppression * feat: Enhance DATA_EXFIL findings with destination field tracking in diagnostics and SARIF output * feat: Add tainted body and URL handling for data exfiltration detection * feat: Add integration tests and fixtures for DATA_EXFIL and SSRF detection in Go * feat: Add Java integration tests and fixtures for DATA_EXFIL detection across multiple HTTP clients * feat: Add synthetic externals handling for closure-captured variables in SSA * feat: Implement closure-based suppression for resource leak findings * feat: Add regression guards for shell-injection and taint propagation in for-of destructure patterns * feat: Implement constructor cap narrowing for data exfiltration detection in HTTP request builders * feat: Add gated sinks for data exfiltration detection in C and C++ using curl_easy_setopt * feat: Implement DATA_EXFIL cap parity for backwards analysis and add integration tests * feat: Add data exfiltration sinks for various languages and enhance documentation * refactor: Simplify formatting and improve readability in various files * refactor: Improve readability by simplifying conditional statements and adding clippy linting * docs: Update CHANGELOG and comments for data exfiltration features and configuration * docs: Clarify configuration instructions for data exfiltration trusted destinations * docs: Enhance comments for evidence routing logic in data exfiltration
15 lines
654 B
JavaScript
15 lines
654 B
JavaScript
// DATA_EXFIL silenced regression fixture: plain user input echoed into the
|
|
// body of an outbound `fetch` to a fixed URL must NOT fire `Cap::DATA_EXFIL`.
|
|
// The user already controls `req.body.message` — surfacing it back into the
|
|
// request payload is not a cross-boundary disclosure. This is the canonical
|
|
// false-positive class for API gateways and telemetry forwarders that proxy
|
|
// `req.body`, killed by the source-sensitivity gate in `ast.rs`.
|
|
//
|
|
// Driven by `fetch_data_exfil_integration_tests.rs`.
|
|
function forward(req) {
|
|
var payload = req.body.message;
|
|
fetch('/endpoint', {
|
|
method: 'POST',
|
|
body: payload,
|
|
});
|
|
}
|