Live data from Hacker News

Viewing profile — accessvector

accessvector

HN member
Joined
Sun, Jul 31, 2022, 1:41 PM UTC
HN karma
105
Public activity
18 items

About accessvector

https://accessvector.net/

Recent public activity

  1. story
  2. comment
    Comment #39659494

    Richard StaLLMan?

  3. comment
    Comment #39652924

    Thanks for your work in making an excellent tool; I, and many of my coworkers, use this. The price point is entirely fair and it’s a pleasure to use every time. But - above this - …

  4. story
  5. comment
    Comment #38732926

    I started programming with QBASIC at about 10 years old, too, after randomly coming across a book called “Practise Your BASIC”. It’s a great book and Usborne recently released it f…

  6. comment
    Comment #38626235

    Right, so this is the crux of the vulnerability. Firstly, note that the `MAX` macro is defined as: #define MAX(a, b) ((a) > (b) ? (a) : (b)) This is important because it doesn't ca…

  7. comment
    Comment #38616405

    Consider this: struct pinsyscall entries[] = { { .sysno = 1, .offset = 0x1234 }, { .sysno = 2, .offset = 0x5678 }, { .sysno = 1, .offset = 0x9abc } }; Now `nsyscalls` will be 3 and…

  8. comment
    Comment #38614016

    Just to handle the case where the same syscall number is specified twice by the ELF header: in that case, the entry is set to -1 (presumably meaning it’s invalid).

  9. comment
    Comment #38612669

    Re-reading this, my analysis is slightly incorrect: the `MAX` at [5] with an unsigned arg means we can make `npins` an arbitrary `int` using the loop at [4]. Choosing to make `npin…

  10. comment
    Comment #38610943

    Out-of-bounds heap write happens in this function: int elf_read_pintable(struct proc *p, Elf_Phdr *pp, struct vnode *vp, Elf_Ehdr *eh, uint **pinp) { struct pinsyscalls { u_int off…

  11. comment
    Comment #37285427

    Spoiler for anyone else that got excited: nothing new has been published.

  12. comment
  13. story
  14. story
  15. story
  16. comment
    Comment #32523517

    A pretty boring (non-exploitable) yet widespread use-after-free vulnerability that was recently patched and affected Linux kernels since ~2013. It involves a race condition between…

  17. story
  18. story