Revisiting unresolved JetBrains TeamCity issues: https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=teamcity

• TeamCity 2024.07.3
  • Release/Blog Publish Date: 01 October 2024
    CVE assigned/publicly available: 08 October 2024 (8 days)
  • "5 security problems have been fixed."
    5 CVEs assigned
• TeamCity 2024.07.2
  • Release/Blog Publish date: 29 August 2024
    CVEs: N/A
  • "3 security problems have been fixed."
    0 CVEs assigned
• TeamCity 2024.07.1
  • Release/Blog Publish date: 06 August 2024
    CVE assigned/publicly available: 16 August 2024 (11 days)
  • "6 security problems have been fixed."
    5 CVEs assigned
• TeamCity 2024.07
  • Release/Blog Publish Date: 18 July 2024
    CVE assigned/publicly available: 22 July 2024 (5 days)
  • "19 security problems have been fixed."
    6 CVEs assigned

I may be a hater but I'm not lying and to my customers and hiding security issues.

#jetbrains #teamcity #vulnerability #cve

@screaminggoat @dreadpir8robots @h4sh @todb Full Disclosure

@screaminggoat @dreadpir8robots @todb @h4sh IME CVE issuance is the easiest part: if vendor is a CNA, they will take care of it, most of the process is coordinating technical details and disclosure. If it's MITRE you can get a CVE basically instantly with their online form.

I have to note that AFAIK MITRE is *not* a fallback (they will redirect you to the CNA you just visited), and H1 is *definitely* not a fallback (for a multitude of reasons). FD is a fallback, and so is CERT-CC in some cases.

social media platform users are going to link offsite. the only question is how obnoxious the platform will make it for them and everyone else.

(For context: Instagram prohibits links in post text. This, plus the incentive to inflate comments, has led to the proliferation of tools where creators instruct their followers to comment with a specific word to receive a link in their DMs— in this case, to a pie crust recipe)

@wdormann Is this the feature implemented by ai.exe, aka. "Artificial Intelligence Host"? That thing caused problems for me before by trying to chat with the mothership:

https://www.reddit.com/r/Office365/comments/ylkip5/comment/j3vjm8w/

[RSS] RISC CPU Lives in Excel

https://hackaday.com/2024/11/24/risc-cpu-lives-in-excel/

and... fruitless

$1$yMKkNlnT$BDBNp1JZAq1Kyk.CUV4Vd0

Maybe I can nerdsnipe this?

From Guardian to Gateway: The Hidden Risks of EDR Vulnerabilities - Neodyme
https://neodyme.io/en/blog/wazuh_rce/

/via @tekwizz123

CVE-2024-32038, CVE-2023-50260
#frombsky

@aardrian That's weird, it usually works for me out of the box :( I'm not in the mood of digging into Medium's bullshit, but the link at the top of the article seems to work. Anyway, sorry for the spam!

@aardrian https://scribe.rip

Page-Oriented Programming: Subverting Control-Flow Integrity of Commodity Operating System Kernels with Non-Writable Code Pages | USENIX
https://www.usenix.org/conference/usenixsecurity24/presentation/han-seunghun

/via @andersonc0d3

Prefer Rust to C? There's no reason your decompilation has to necessarily target C as the output. With our Language Representation UI/API in 4.2 you can see all your decompilation as Rust instead.

@kaaswe Ugh, I guess this is how UX gets in the way the worst possible time (the middle of an incident) :P

@kaaswe Have some empathy then :)

@kaaswe Red Team likes this

A bit annoying thing in #Bsky #ATProto is that you don't post plaintext that is "enriched" remotely, but provide a Rich Text object with links, tags, etc. marked as such. It seems from the servers perspective len(rich_text)!=len(str(rich_text)) and I found no way to find out what the true length of my rich Text object will be resulting in failed posts and bad thread splitting...

https://atp.readthedocs.io/en/latest/atproto_client/utils/text_builder.html

@tmr232 There are bunch of helper scripts used during the build as far as I can tell (the RMI Debugger feature in particular came up in the stack trace but didn't investigate further).

Latest #Ghidra failed to build because some obscure pyOpenSSL error, which can break pip altogether:

> TypeError: deprecated() got an unexpected keyword argument 'name'

Here's what worked for me:
- Delete the failing pyOpenSSL directory from site-packages
- pip install "pyOpenSSL>22.0.0,<23.0"

@infosecdj That's weird, I'd think chemistry is so widely applicable that there's always need for it. I guess it's not true for every subfield?