mandiant / mandiant/capa-rules
reference RSA key
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 736
- Forks
- 245
- Avg merge
- 4d 53m
- Merged PRs (30d)
- 2
Description
see related rule `reference public RSA key`
Bytes and/or numbers for the structures detailed here:
- https://docs.microsoft.com/en-us/windows/win32/api/wincrypt/ns-wincrypt-rsapubkey
- https://docs.microsoft.com/en-us/windows/win32/api/wincrypt/ns-wincrypt-publickeystruc
E.g.
```
- number: 0x??31415352
- number: 0x??33415352
```
Set to RSA1 (0x31415352) for public keys and to RSA2 (0x32415352) for private keys.
Example code
```asm
mov rax, 80031415352h
mov [rdi], rax
mov byte ptr [rdi+8], 3
mov rcx, rdi
add rcx, 9 ; Dst
lea rdx, qword_140030000 ; Src
mov r8d, 112h ; MaxCount
call memmove
```
```asm
mov rax, 80033415352h
mov [rdi], rax
mov byte ptr [rdi+8], 3
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the related `reference public RSA key` rule and reviewing the Microsoft `RSAPUBKEY` and `PUBLICKEYSTRUC` references linked in the issue. Add coverage for the RSA1 and RSA2 values shown in the examples, including their byte or number representations, and verify the rule recognizes the supplied instruction patterns.
Written by the indexing model from the issue text.
Assessment
- Domain
- reverse-engineering, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100