added version info and upstream reference.

This commit is contained in:
Pedro Sampaio 2020-03-16 11:35:27 -03:00 committed by GitHub
parent 2cb7deee02
commit 8eda7a010e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -18,7 +18,7 @@
"version": {
"version_data": [
{
"version_value": "n/a"
"version_value": "2.7.x, 2.8.x, 2.9.x"
}
]
}
@ -47,6 +47,11 @@
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1740",
"name": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1740",
"refsource": "CONFIRM"
},
{
"url": "https://github.com/ansible/ansible/issues/67798",
"name": "https://github.com/ansible/ansible/issues/67798",
"refsource": "CONFIRM"
}
]
},
@ -54,7 +59,7 @@
"description_data": [
{
"lang": "eng",
"value": "A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes \"ansible-vault edit\", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely."
"value": "A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes \"ansible-vault edit\", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable."
}
]
},