GCVE - cpe:2.3:a:diboot:diboot-core:*:*:*:*:*:*:*:*

Approved changes feed: RSS · Atom

cpe:2.3:a:diboot:diboot-core:*:*:*:*:*:*:*:*

part: a version: * update: *

Notes

Imported from gcve-enriched-dumps CVE data

PURL	Source	Last updated
No PURL mappings for this CPE yet.

Identifier	cpeApplicability	Submitted	db.gcve.eu details	Rationale
`CVE:CVE-2026-70557`	vulnerable	2026-09-16 04:33:00.910665	diboot-core Authenticated Arbitrary Field Read via loadRelatedData Discloses Password Hashes and Salts MEDIUM (6.5) diboot-core's POST /common/load-related-data endpoint resolves caller-supplied field names to any @TableField column of any entity and returns those values for all rows, with no field or entity allowlist. The only guard, relatedDataSecurityCheck(), returns true unconditionally, so any authenticated user (including a zero-role account) can read @JsonIgnore-annotated secret fields such as IamAccount.authSecret and IamAccount.secretSalt for every account, or arbitrary secret fields of any other entity. Shiro's two-iteration MD5 with an 8-character salt is trivially crackable offline, so the disclosed admin password hashes convert to full administrative takeover. The endpoint is not example code; the official diboot-admin-ui frontend requires it, so deployments following the vendor's recommended integration expose it. The mechanism was renamed relatedData* to attachMore* on the development branch, but attachMoreSecurityCheck() also returns true unconditionally. Published: 2026-08-06T19:16:18.724Z Updated: 2026-11-08T14:08:25.829Z Open on db.gcve.eu Reference links https://github.com/dibo-software/diboot https://github.com/dibo-software/diboot/issues/104	Imported from gcve-enriched-dumps CVE data

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.