OWASP / www-project-top-10-for-large-language-model-applications

OWASP Foundation Web Respository
Other
526 stars 134 forks source link

LLM06 Typo in all (3) Resources + Proposed Fixes #197

Closed nicholasgrove closed 10 months ago

nicholasgrove commented 1 year ago

Issue

# Where: LLM06 typo in all (3) Resources (Presentation, Whitepaper, Google Doc) # Current:

"LLMs may inadvertently reveal confidential data in its responses, leading to unauthorized data access, privacy violations, and security breaches."

# Proposed:

"LLMs may inadvertently reveal confidential data in their responses, leading to unauthorized data access, privacy violations, and security breaches."

# Justification: The possessive pronoun "its" should be edited to "their" because "LLMs" are plural.

Notes

  1. Potential labels: "bug" + "llm-06"
  2. ❤️ y'all, hope this helps.
GangGreenTemperTatum commented 11 months ago

Hey @nicholasgrove , I don't see this in the latest entry for LLM06, can you provide a direct link/ref? Please refer to all v1.1 docs (current version). TYIA!

nicholasgrove commented 10 months ago

Hi @GangGreenTemperTatum ! All these refer to the:

  1. Website (https://llmtop10.com/)
  2. 1.1 PDF (https://owasp.org/www-project-top-10-for-large-language-model-applications/assets/PDF/[OWASP-Top-10-for-LLMs-2023-v1_1.pdf](https://owasp.org/www-project-top-10-for-large-language-model-applications/assets/PDF/OWASP-Top-10-for-LLMs-2023-v1_1.pdf)
  3. And 1.1 slides (https://owasp.org/www-project-top-10-for-large-language-model-applications/assets/PDF/[OWASP-Top-10-for-LLMs-2023-slides-v1_1.pdf](https://owasp.org/www-project-top-10-for-large-language-model-applications/assets/PDF/OWASP-Top-10-for-LLMs-2023-slides-v1_1.pdf)

And still stand today (11/21/23). HTH!

GangGreenTemperTatum commented 10 months ago

LLMs may inadvertently reveal confidential data in its responses, leading to unauthorized data access, privacy violations, and security breaches.

Thanks @nicholasgrove

See my repo search for your string

image

I don't understand where your seeing this... the word "inadvertently" isn't even used in a current entry

GangGreenTemperTatum commented 10 months ago

Oh, I found it, its in the summary page which is not extracted from a vulnerability entry

image

@rossja i'll update the current v1.1 Figma which we will clone for v2.0 and therefore inherit this fix

Thanks @nicholasgrove !