> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/product-advisories/historical-notices/readers-credentials-and-locks/mifare-desfire-and-mifare-plus-key-security-advisory-december-2020.md).

# MIFARE DESFire and MIFARE Plus key security advisory - December 2020

Review the exposed default MIFARE DESFire and MIFARE Plus key and affected credentials.

### Overview![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

We have become aware that the Default Gallagher MIFARE DESFire and MIFARE Plus key has been exposed and was published at 9:30am on the 16th of December NZDT. This act means that cards using the default key can be cloned or emulated, resulting in a site’s security becoming compromised.

This vulnerability does not affect Gallagher Mobile Connect credentials, US Government FIPS201 PIV cards, GovPass, MIFARE DESFire with a site-specific key, or MIFARE Plus with a site-specific key. Any sites who installed a new Gallagher solution from Command Centre v8.20 onwards will also be unaffected, unless they have reverted to using the default key.\
\
MIFARE Classic and 125kHz cards are also unaffected by this vulnerability; however, as these cards are compromised technology, their use is not recommended by us.

Channel Partners and Customers were emailed December 2020. Marketing collateral is available on request.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/product-advisories/historical-notices/readers-credentials-and-locks/mifare-desfire-and-mifare-plus-key-security-advisory-december-2020.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
