Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A Android-IMSI-Catcher-Detector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CellularPrivacy
  • Android-IMSI-Catcher-Detector
  • Issues
  • #31
Closed
Open
Issue created Apr 12, 2014 by Administrator@rootContributor

Possible Security Exploit

Created by: E3V3A

Apparently AIMSICD is debuggable, hopefully because its needed, but possibly because it was forgotten. According to this page , debuggable Apps can be a security risk.

The way to check is:

cat /data/system/packages.list | grep AIMSICD

If the 3rd field is "1", it is debuggable. (You should check all your Apps!)

Then you can also check by pulling the app and then viewing the App's AndroidManifest.xml file with:

aapt d xmltree com.name.apk

jdwp-control = Java Debug Wire Protocol

More info is to be found at Blackhat Media. Can you fix this, @xLaMbChOpSx?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Assignee
Assign to
Time tracking