{"answers":{"affected":"1 open source package ship an affected version, including github.com/bincyber/go-sqlcrypter.","exploited":"There is no known exploitation of GO-2024-2451 in the wild and no public exploit code.","fix":"No fix has been published for GO-2024-2451 yet. Limit exposure of the affected software until one is available.","what":"GO-2024-2451 is a vulnerability in github.com/bincyber/go-sqlcrypter, published on 30 Jan 2024."},"fix_prompt":"Check this codebase for GO-2024-2451 and fix it if it is affected.\n\nWhat it is: GO-2024-2451 is a vulnerability in github.com/bincyber/go-sqlcrypter, published on 30 Jan 2024. \nExploitation: There is no known exploitation of GO-2024-2451 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/bincyber/go-sqlcrypter (Go): affected from 0.1.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GO-2024-2451/ (Markdown: https://insights.sbomify.com/GO-2024-2451/index.md)","id":"GO-2024-2451","markdown":"https://insights.sbomify.com/GO-2024-2451/index.md","name":"GO-2024-2451","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["data_read"],"network_reachable":"unknown","non_default_config":false,"product_category":"Go encryption library","requires_auth":"none","summary":"An attacker with access to ciphertexts can decrypt all messages if IV collisions occur due to excessive encryption under the same key.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"There is a risk of an IV collision using the awskms or aesgcm provider. NIST SP 800-38D section 8.3 states that it is unsafe to encrypt more than 2^32 plaintexts under the same key when using a random IV. The limit could easily be reached given the use case of database column encryption. Ciphertexts are likely to be persisted and stored together. IV collision could enable an attacker with access to the ciphertexts to decrypt all messages encrypted with the affected key.\n\nThe aesgcm provider cannot be fixed without a breaking change, so users should not encrypt more than 2^32 values with any key. The awskms package can be fixed without a breaking change by switching to a counter-based IV.","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"IV collision in github.com/bincyber/go-sqlcrypter","id":"GO-2024-2451","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0.1.0"],"last_affected":[],"package":"github.com/bincyber/go-sqlcrypter","purl":"pkg:golang/github.com/bincyber/go-sqlcrypter","source":"GO-2024-2451"}],"products":null,"published":"2024-01-30","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker with access to ciphertexts can decrypt all messages if IV collisions occur due to excessive encryption under the same key.","url":"https://insights.sbomify.com/GO-2024-2451/"}