CVE-2018-17232: SQL injection vulnerability in archivebot.py in docmarionum1 Slack ArchiveBot (aka slack-archive-bot) before 2

Q: How do I fix CVE-2018-17232?

slack archivebot: upgrade to 2018-09-19. Exact commands for each OS are on this page.

Q: Is CVE-2018-17232 being exploited?

CVE-2018-17232 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-17232 affect?

CVE-2018-17232 affects slack archivebot. Severity is critical (CVSS 9.8). SQL injection vulnerability in archivebot.py in docmarionum1 Slack ArchiveBot (aka slack-archive-bot) before 2018-09-19 allows remote attackers to execute arbitrary SQL commands via the text parameter to cursor.execute().

Q: How urgent is CVE-2018-17232?

Priority 59/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2018-17232 is a critical-severity flaw (CVSS 9.8) affecting slack archivebot. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SQL injection vulnerability in archivebot.py in docmarionum1 Slack ArchiveBot (aka slack-archive-bot) before 2018-09-19 allows remote attackers to execute arbitrary SQL commands via the text parameter to cursor.execute().

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 22%)
CISA exploited list	No
Weakness	CWE-89
Published	2018-09-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: slack archivebot project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-09-20 06:29 UTCPublished CVE record published
2026-06-17 01:45 UTCUpdated Record last modified

slack archivebot project slack archivebot UPGRADE

Affected: < 2018-09-19

Fixed in: 2018-09-19

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy slack-archivebot || rpm -q slack-archivebot || slack-archivebot --version

2. UPGRADE to 2018-09-19 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade slack-archivebot

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade slack-archivebot

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-17232?

slack archivebot: upgrade to 2018-09-19. Exact commands for each OS are on this page.

Is CVE-2018-17232 being exploited?

CVE-2018-17232 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-17232 affect?

CVE-2018-17232 affects slack archivebot. Severity is critical (CVSS 9.8). SQL injection vulnerability in archivebot.py in docmarionum1 Slack ArchiveBot (aka slack-archive-bot) before 2018-09-19 allows remote attackers to execute arbitrary SQL commands via the text parameter to cursor.execute().

How urgent is CVE-2018-17232?

Priority 59/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Slack vulnerabilities

References

← Back to latest CVEs