Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security: Checksec JSON output keys are not reliable #94

Open
Wenzel opened this issue Apr 17, 2020 · 0 comments
Open

Security: Checksec JSON output keys are not reliable #94

Wenzel opened this issue Apr 17, 2020 · 0 comments
Labels
checksec checksec related issue Upstream Upstream bug in a library

Comments

@Wenzel
Copy link
Owner

Wenzel commented Apr 17, 2020

Checksec's JSON should contain a key which is the filepath:

~/Projets/oswatcher/tools/checksec/checksec --output=json --file=/usr/bin/xz | jq .

{
  "/usr/bin/xz": {
    "relro": "full",
    "canary": "yes",
    "nx": "yes",
    "pie": "yes",
    "rpath": "no",
    "runpath": "no",
    "symbols": "no",
    "fortify_source": "yes",
    "fortified": "5",
    "fortify-able": "8"
  }
}

However, some files are indexed by a file key, and not by their filepath:

~/Projets/oswatcher/tools/checksec/checksec --output=json --file=klibc-usBAintlt99f0TITo98H_trqH2c.so | jq .

{
  "file": {
    "relro": "no",
    "canary": "no",
    "nx": "no",
    "pie": "no",
    "rpath": "no",
    "runpath": "no",
    "symbols": "no",
    "fortify_source": "no",
    "fortified": "0",
    "fortify-able": "0"
  }
}
@Wenzel Wenzel added Upstream Upstream bug in a library checksec checksec related issue labels Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
checksec checksec related issue Upstream Upstream bug in a library
Projects
None yet
Development

No branches or pull requests

1 participant