vciy

CVE-2017-15705

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A denial of service vulnerability was identified that exists in Apache SpamAssassin before 3.4.2

CVE-2017-157054 of 4 sources documented this
23

rank 23 = 2 + 13 + 0 + 8 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.07879  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from NVD  ·  without this subject the record ranks 10

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 23

How much of the world it touches

NVD CPE configurations

10 products in the CPE ranges  ·  without this subject the record ranks 15

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 23

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$94,500over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$94,500 = $4.99M incident cost x 0.24048551839932833 exposure x 0.07879 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.07879EPSSNOT IN KEVas of 2026-09-20
Severity5.3 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementsteadyreceipt
PLATEAU10Minimal movement since 2021-04-14, 1971 days at 0.08, as of 2026-09-06. arc-rules@v1

Foresight · where to check next

CVE-2022-47966CVE-2022-29499VMware vCenterApache Log4j2QNAP Systems Inc.Microsoft15705

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Apache SpamAssassin? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactPartial availability lossreceipt
Scored fromCVSS v3.0 · NVD's vectorreceipt
Weakness classCWE-20 Improper Input Validationreceipt
Published consequencesCWE-20: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory); Confidentiality: Read Memory, Read Files or Directories…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchspamassassin 3.4.2receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD5.3 MEDIUMreceipt
Exploit probability0.07879 · top 6% of all CVEsreceipt
Blast breadth7 products across 4 vendorsderived
Assigned byapachereceipt
Recorded changes23 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productApache Software Foundation Apache SpamAssassinreceipt
Published rangesapache spamassassin < 3.4.2; canonical ubuntu linux 12.04; canonical ubuntu linux 14.04; canonical ubuntu linux 16.04receipt
Show all 10 published ranges
apache spamassassin < 3.4.2
canonical ubuntu linux 12.04
canonical ubuntu linux 14.04
canonical ubuntu linux 16.04
canonical ubuntu linux 18.04
debian linux 8.0
redhat enterprise linux desktop 7.0
redhat enterprise linux eus 7.5
redhat enterprise linux server 7.0
redhat enterprise linux workstation 7.0

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

A denial of service vulnerability was identified that exists in Apache SpamAssassin before 3.4.2. The vulnerability arises with certain unclosed tags in emails that cause markup to be handled incorrectly leading to scan timeouts. In Apache SpamAssassin, using HTML::Parser, we setup an object and hook into the begin and end tag event handlers In both cases, the "open" event is immediately followed by a "close" event - even if the tag *does not* close in the HTML being parsed. Because of this, we are missing the "text" event to deal with the object normally. This can cause carefully crafted emails that might take more scan time than expected leading to a Denial of Service. receipt

Read the rest of the CNA's description

The issue is possibly a bug or design decision in HTML::Parser that specifically impacts the way Apache SpamAssassin uses the module with poorly formed html. The exploit has been seen in the wild but not believed to have been purposefully part of a Denial of Service attempt. We are concerned that there may be attempts to abuse the vulnerability in the future.

NVD's analysis a second authority

severity
5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
weakness
CWE-20
affected versions
apache spamassassin < 3.4.2; canonical ubuntu linux 12.04; canonical ubuntu linux 14.04; and 7 more, listed in full below

check it yourself usn.ubuntu.com usn.ubuntu.com security.gentoo.org lists.apache.org access.redhat.com securityfocus.com +2 morereceipt

Movement the material steps

14 Apr 20210.06653
7 Mar 20230.00799 · scoring model v2023.03.01
17 Mar 20250.0342 · scoring model v2025.03.14
15 Jun 20260.07879 · scoring model v2026.06.15
6 Sep 20260.07879
Show all 23 observations
14 Apr 20210.06653
4 Feb 20220.01859
7 Mar 20230.00799
8 Jul 20230.00665
11 Sep 20230.00735
8 Nov 20230.01470
8 Feb 20240.01041
18 Mar 20240.00853
5 May 20240.00891
1 Jul 20240.00912
17 Dec 20240.02683
21 Dec 20240.01909
17 Mar 20250.0342
29 Mar 20250.04283
30 Mar 20250.0342
3 Jul 20250.03357
20 Jul 20250.01839
18 Aug 20250.01771
15 Jun 20260.07879
23 Aug 20260.07376
30 Aug 20260.07879
5 Sep 20260.07376
6 Sep 20260.07879

23 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.07879Published2018-09-17Index as of2026-09-06

The record had been public for 7 years, 11 months when this index was last written.

Published 2018-09-17 receipt · Index as of 2026-09-06 derived

The pattern, elsewhere

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2022-47966matches 5 of 8KEV listed · 2023receipt
CVE-2022-29499matches 5 of 8KEV listed · 2022receipt
CVE-2021-21985 · VMware vCenter Server and VMware Cloud…matches 5 of 9KEV listed · 2021receipt
CVE-2021-44228 · Apache Log4j2matches 5 of 9KEV listed · 2021receipt
CVE-2018-19949 · QNAP Systems Inc. QTSmatches 5 of 9KEV listed · 2020receipt
CVE-2019-0604 · Microsoft SharePoint Servermatches 5 of 9KEV listed · 2019receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

13347 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2017-15705.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.