Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

stix bundle download was unsuccessful

Open
#397 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, python

Research direction

Start with update-attack.py and reproduce the STIX bundle download against the reported /api/stix-bundles/?domain=enterprise-attack endpoint. Check how the script handles the Workbench login and the endpoint's Not Authorized response; done means the v12.1 bundle downloads successfully in the reported setup.

Written by the indexing model from the issue text.

Description

Github
Hi team,

So I am trying to sync my ATT&CK workbench with the ATT&CK website. It is currently hosting on a virtual machine in Azure.

When I tried to do this setup way earlier, I did not have any issue, but now when I try to run the python3 update-attack.py, I get this error "http://localhost/api/stix-bundles/?domain=enterprise-attack stix bundle download was unsuccessful"

I tried to troubleshoot the issue as to what has changed from the last time I tried this on my local virtual machine. I can make the following observations:

  1. The version of workbench used is newer compared to the one I had worked with before.
  2. There is a login capability for Workbench.
  3. When I try to view the stix bundle page, I get the message Not Authorized. This message is only fixed when I login into the Workbench and then try again to view the page.

Is this a known Bug/error, please let me know. Also, the version of ATT&CK I was trying to use was the latest one (v12.1)

Dominant language
HTML
Stars
588
Forks
174
Avg merge
3d 11h
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mitre-attack/attack-website

All issues in mitre-attack/attack-website

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.