Exposure of Sensitive Information Through Metadata in GitHub repository answerdev/answer prior to 1.0.8.
The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Answer | Answer | * | 1.0.8 (excluding) |
Developers might correctly prevent unauthorized access to a database or other resource containing sensitive information, but they might not consider that portions of the original information might also be recorded in metadata, search indices, statistical reports, or other resources. If these resources are not also restricted, then attackers might be able to extract some or all of the original information, or otherwise infer some details. For example, an attacker could specify search terms that are known to be unique to a particular person, or view metadata such as activity or creation dates in order to identify usage patterns.