[device_info_plus] Release APK contains debug-enabled dependency (com.deviceinsight.commons.BuildConfig.DEBUG=true)

Aberta
#4,015 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
dart, flutter
Domínio
mobile, security

Direção de pesquisa

Start by inspecting device_info_plus's Android build configuration and how it packages com.deviceinsight.commons.BuildConfig into release APKs; the issue does not name those files. Check whether the reported DEBUG value enables functionality or is simply generated metadata, then verify it in a release artifact. Done means confirming whether this is an expected false positive or identifying a production security concern for maintainers to address.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

question
What is your question?

During a penetration test, the Android application was reported as containing a debug-enabled dependency.

The finding points to:

com/deviceinsight/commons/BuildConfig.java

The security assessment indicates that debug-related configuration is included in the final production build. Production artifacts should not expose debugging functionality or debug-enabled configurations.

Reported classification:

CWE-919: Weaknesses in Mobile Applications
OWASP Mobile Top 10: M1 Improper Platform Usage
OWASP MASVS: MSTG-RESILIENCE-2
Could the maintainers please verify whether:

The library is intentionally shipping debug configuration in release artifacts.
Any debug-only functionality remains accessible in production builds.
The generated BuildConfig values are expected and pose no security risk.
The purpose of this issue is to understand whether the reported penetration test finding is a false positive or if there is a security concern that should be addressed.

device_info_plus: 11.1.1
Flutter: 3.41.6

Checklist before submitting a question
  • I searched issues in this repository and couldn't find such bug/problem
  • I Google'd a solution and I couldn't find it
  • I searched on StackOverflow for a solution and I couldn't find it
  • I read the README.md file of the plugin
  • I am using the latest version of the plugin
  • All dependencies are up to date with flutter pub upgrade
  • I did a flutter clean
  • I tried running the example project
Linguagem predominante
Dart
Estrelas
1.9k
Forks
1.3k
Merge médio
1h 7min
PRs com merge (30d)
1

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de fluttercommunity/plus_plugins

Todas as issues de fluttercommunity/plus_plugins

Issues semelhantes

Mais issues de Dart

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.