You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lécharny (Jira)" <ji...@apache.org> on 2026/09/28 10:45:00 UTC

[jira] [Commented] (DIRAPI-439) Hostile server subschema bytecode is class-loaded and instantiated on the client

    [ https://issues.apache.org/jira/browse/DIRAPI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120098#comment-18120098 ] 

Emmanuel Lécharny commented on DIRAPI-439:
------------------------------------------

A system property, _org.apache.directory.api.ldap.schema.loader.allowBytecodeLoading_, has been added.

By default, byte code won't be loaded.

> Hostile server subschema bytecode is class-loaded and instantiated on the client
> --------------------------------------------------------------------------------
>
>                 Key: DIRAPI-439
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-439
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 2.1.8
>            Reporter: Emmanuel Lécharny
>            Priority: Major
>             Fix For: 2.1.9
>
>
> A rogue/compromised *LDAP* server (or pre-*TLS* *MITM*) answers a client's _loadSchema()_ subschema search with '_syntaxCheckers_: 
> {code:java}
> ( 1.2.3.4 FQCN evil.Pwn BYTECODE <base64 of a class whose static{} runs Runtime.exec> X-SCHEMA "other" )
> {code}
> _DefaultSchemaLoader_ parses it, _SchemaEntityFactory_ defines the class via _AttributeClassLoader_ and instantiates it — attacker code executes in the client *JVM* with the application's privileges.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org