Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TechniqueCapec.json is empty #38

Closed
jiangdie666 opened this issue Jul 3, 2023 · 3 comments · Fixed by #39
Closed

TechniqueCapec.json is empty #38

jiangdie666 opened this issue Jul 3, 2023 · 3 comments · Fixed by #39

Comments

@jiangdie666
Copy link

After the container bronbootstrap finished downloading the data, there should be something wrong when associating the capec and technique data, resulting in no data transfer with the database.
image
When checking the front end of the database, I found that all other data were intact, only TechniqueCapec was empty.
image
At first I thought there was a problem with the transfer, so I opened the container to check the TechiniqueCapec.json and found that it was empty, but the capec.json and Techinique.json were normal.
image
Please allow me to ask if there is some problem with the code that causes the association to fail.

@hembergerik
Copy link
Contributor

Thanks. I will look into it. It could be that the input data for techniques and/or CAPEC has changed.

@jiangdie666
Copy link
Author

There is a small problem, I read the code did not find how the cpe data is saved, he is from the cve configurations field cpe23Uri extracted one by one?

hembergerik added a commit that referenced this issue Jul 4, 2023
…EC entry. Previously the ATTACK technique entry could have a link to capec. Fix #38
hembergerik added a commit that referenced this issue Jul 4, 2023
…EC entry. Previously the ATTACK technique entry could have a link to capec. Fix #38 (#39)
@hembergerik
Copy link
Contributor

Hopefully #39 fixes the issue of Technique and CAPEC links.

Yes, the cpe uris are extracted one by one. I do not believe this should affect the issue. I think it had to do with a change in the ATT&CK data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants