Skip to content

[FIX ISSUE FALSE-POSITIVE] CVE-2025-14847: High False Positives on Non-MongoDB#15579

Merged
ritikchaddha merged 1 commit intomainfrom
FALSE-POSITIVE]-CVE-2025-14847-High-False-Positives-on-Non-MongoDB
Mar 12, 2026
Merged

[FIX ISSUE FALSE-POSITIVE] CVE-2025-14847: High False Positives on Non-MongoDB#15579
ritikchaddha merged 1 commit intomainfrom
FALSE-POSITIVE]-CVE-2025-14847-High-False-Positives-on-Non-MongoDB

Conversation

@Akokonunes
Copy link
Copy Markdown
Contributor

Fix CVE-2025-14847 FPs: reversed flow to tcp(1) && javascript(1) so TCP fingerprints MongoDB first. Added isMongoDBResponse() opcode guard, removed loose 10+ printable-string leak detection, added missing 4.4/4.2/4.0/3.6 version ranges.

PR Information

  • Fixed CVE-2020-XXX / Added CVE-2020-XXX / Updated CVE-2020-XXX
  • References:

Template validation

  • Validated with a host running a vulnerable version and/or configuration (True Positive)
  • Validated with a host running a patched version and/or configuration (avoid False Positive)

Additional Details (leave it blank if not applicable)

Additional References:

@neo-by-projectdiscovery-dev
Copy link
Copy Markdown

neo-by-projectdiscovery-dev bot commented Mar 10, 2026

Neo - Nuclei Template Review

No security issues found

Highlights

  • Flow reversal from || to && makes detection more restrictive - TCP fingerprinting now required before exploit attempt
  • Added isMongoDBResponse() function validates MongoDB protocol opcodes (OP_REPLY=1, OP_MSG=2012, OP_COMPRESSED=2013) to prevent false positives on HTTP/SSH/other services
  • Removed loose string extraction logic that triggered on any 10+ character printable sequence - now focuses on BSON error patterns
  • Added missing vulnerable version ranges (3.6, 4.0, 4.2, 4.4) to improve coverage per CVE advisory
  • TCP fingerprinting (buildInfo command) now mandatory first step - validates target is MongoDB before sending exploit payload
Hardening Notes
  • PR validation checkboxes are unchecked - recommend testing against vulnerable MongoDB instances (versions 3.6 through 8.2) and non-MongoDB services to verify false positive reduction
  • The removal of generic string extraction is a deliberate trade-off: significantly reduces false positives but may miss edge case memory leaks that don't contain BSON error markers
  • Consider running parallel detection with old/new templates temporarily to compare detection rates before full rollout
  • Template represents security-positive change: stricter protocol validation, mandatory fingerprinting, and focused leak detection patterns

Comment @pdneo help for available commands. · Open in Neo

@github-actions github-actions bot requested a review from ritikchaddha March 10, 2026 01:54
@Akokonunes
Copy link
Copy Markdown
Contributor Author

@pdneo review

@Akokonunes Akokonunes added the Done Ready to merge label Mar 11, 2026
Refactor CVE-2025-14847 YAML file to enhance clarity and detail. Update descriptions, remediation steps, and add additional references.
@Akokonunes Akokonunes force-pushed the FALSE-POSITIVE]-CVE-2025-14847-High-False-Positives-on-Non-MongoDB branch from 8d101ad to b000406 Compare March 12, 2026 11:24
@ritikchaddha ritikchaddha merged commit fbffea1 into main Mar 12, 2026
3 checks passed
@ritikchaddha ritikchaddha deleted the FALSE-POSITIVE]-CVE-2025-14847-High-False-Positives-on-Non-MongoDB branch March 12, 2026 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Done Ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FALSE-POSITIVE] CVE-2025-14847: High False Positives on Non-MongoDB Services due to Blind Payload Injection & Flawed Matcher Logic

2 participants