fix: [export_mod/yara_export] escape attribute values in generated YARA string/meta literals

[elhoim]

YaraRule.__str__ in misp_modules/modules/export_mod/yara_export.py interpolated MISP attribute values and meta values (event info, org name, link attributes) directly into double-quoted YARA string literals without escaping backslash or embedded double-quote characters:

for key, values in self.meta.items():
    ...
    result.append(f'        {key} = "{values[0]}"')
    ...
for key, values in self.strings.items():
    ...
    result.append(f'        ${key}_{i} = "{value}"')

Unlike the handle_yara path in the same module, the ruleset built by this class was also never passed through yara.compile() before being returned.

Impact: an attacker-controlled MISP attribute value (or event info / org name) containing a " or \ breaks out of the YARA string literal it was placed in. Depending on the surrounding content this either produces a ruleset that fails to compile in the analyst's YARA engine (an unusable export with no warning from the module) or, more seriously, lets attacker-supplied text be spliced into the rule body as YARA syntax rather than staying inert data — an analyst exporting attributes to a YARA rule has no indication the export is malformed or manipulated until it fails, or misbehaves, downstream.

Fix

Escape \ and " in both the strings-section and meta-section interpolation sites, and compile the fully generated ruleset with yara.compile() before returning it, returning a misperrors response instead of silently emitting an invalid/unsafe ruleset if compilation fails.

Verification

• flake8 on the changed file: clean, no output.
• python -m pytest tests/ against a local misp-modules instance: 161 passed, 4 skipped, 5 subtests passed.

Found during a review of the repository; other findings are being submitted as separate PRs.

🤖 Generated with Claude Code

https://claude.ai/code/session_018dfYpyaSZd1nxSRLr8suj8